Exago Logo
Search
Generic filters
Exact matches only

Search Results for REST ��� SchedulesV2

All Search Results (20)

  • Accessing the Log File

    Exago keeps a text log of when certain tasks are performed. For example each time a page or report is loaded, each time an error occurs or when various phases of execution happen.
    Read More
  • Batch REST API

    A video demonstration on how to effectively manage REST calls using the Batch functionality, and reducing network latency by combining REST calls
    Read More
  • REST - Batch

    Use the Batch REST endpoint to group together multiple sequential calls into a single network request. For environments which make a number of programmatic alterations to the session configuration, Batch can significantly reduce the network load and time to create the session.
    Read More
  • REST - Data Joins

    Joins are the relationship data objects have to each other. Join information is accessible and editable via REST.
    Read More
  • Error Message Glossary

    This article serves as a glossary of error messages that may be displayed during the configuration or use of Exago BI. A list of potential causes and remedies is also included.
    Read More
  • .NET and REST APIs

    A video demonstration of creating application sessions with .NET and REST APIs, then setting the user identification parameters.
    Read More
  • REST - SchedulesV2

    Viewing, creating, modifying, and deleting schedules via the REST Web Service API is available in Exago v2021.1.1+. This feature requires the installation and proper configuration of the Scheduler Service.
    Read More
  • REST - Server Events

    Server events can be accessed for reference and disabled for the session. Server events cannot currently be created or edited using REST.
    Read More
  • REST - Sessions

    Sessions are the means by which REST persists changes through multiple API calls. A REST session allows for you to easily encapsulate a group of user-specific changes.
    Read More
  • User Identification

    User logins must be handled by a security layer in the embedding host application. After a user logs in, the host application should pass identification parameters to the Exago API, which can be used to set permissions on content and data objects within Exago.
    Read More