Configuring Pages in OGL for Orchestrator Studio

You can configure Pages in the OGL platform to filter the content displayed in the OGL widget in Orchestrator Studio. A Page links a guide to a specific application or page and context, ensuring the information appears at the right time.

OGL Pages are updated to reflect where the user is in Studio to facilitate content filtering. For example, you can create an OGL Page so that when a user navigates to the Rules page in Orchestrator Studio, the OGL widget displays only the content related to rules. When you sign in to the Orchestrator Studio, the Pages are Studio and Home. This allows you to share a single OGL application across multiple Oracle products while using an Activation Rule to display Studio-specific content only when the current page is Studio.

For example, when you edit a Switch statement in Logic Extensions, the Pages are Studio, Logic Extensions and Switch. And, when editing a REST Connector, the Pages are Studio, Connector and REST.

For more information on working with OGL editor and creating the OGL content, see the Oracle® Guided Learning User Guide.

To set up a Page in OGL so a specific piece of content (a guide) shows only on a specific Orchestrator Studio page/context, follow these steps:

Access the OGL editor/admin for your OGL application.
Click Settings and select Pages.
In the Pages Manager, add Pages to OGL using the list below to allow showing OGL content based on what page the user is on in Orchestrator Studio.

To display relevant content on the Orchestrator Home page, create Activation Rules to show the content when page is Studio and page is Home. Or just when page is Home if the OGL application is not shared with other applications.

The following Pages are available for filtering:

For example, to activate content on the Form Requests page, add activation rules referencing the 2 pages (Studio, Form Requests).
- Home
- Orchestrations
- Notifications
- Connections
- Connectors
- Run Orchestrations
- Schedules
- White Lists
- Cross References
- Logic Extensions
- Rules
- Form Requests
- Reports
- Watchlists
- Custom Requests
- Messages
- Attachments
- Scheduler
- Workflows
- Widgets
- Import and Export
Connections: (For example, add activation rules referencing the 3 pages (Studio, Connections, and REST).)
- REST
- FTP
- Open API
- Database
- Orchestration
- Enterprise Server AIS
Connectors: (For example, add activation rules referencing the 3 pages (Studio, Connectors, and REST).)
- Orchestration
- REST
- Database
- FTP
- Open API
Custom Requests:(For example, add activation rules referencing the 3 pages (Studio, Custom Requests, and Java)).
- Java
- Script
- Business Function
- Create Array
Rules: (For example, add activation rules referencing the 3 pages (Studio, Rules, and Standard)).
- Standard
- Script
- Java
For Logic Extensions and Workflows, when the user views or edits a node in the diagram, they can view the specific page related to the node.

For example, for an Assignment statement in a Logic Extension, the Pages are Studio, Logic Extensions, and Assignment.

Logic Extensions:
- Assignment
- If Else
- Switch
- While
- Aggregation
- Table IO
- Form Control Function
- Report
- Business Function
- Error
- Start Workflow
- Array Function
- Return
Workflows:
- Report
- Application
- Windows Executable
- Business Function
- Orchestration
- Info Message
- Action Message
- Local Process
- Send Message
- Halt
- Remote Process
Activate the specific guide on the Page (Guide Activation).