An Orange Logic parameter session is a group of parameter changes (configurations) made for a specific feature or project. These changes are intended to be activated, deactivated, or delivered together.
Parameter sessions are often created in test environments so stakeholders can configure and test new workflows before activating them in production environments. Administrators can adjust parameters in their sessions without impacting the configuration of other sessions, allowing them to test changes without impacting other users.
To call an API against a specific session, enter the parameter session ID in the UseSession parameter. You can use this query parameter in any API endpoint.
Orange Logic administrators can find a parameter session ID by copying the link to the session. The session ID is the last part of the link.
Feature Documentation: Parameter sessions
Warning
Parameter sessions only isolate changes to parameters. A parameter is any setting that controls how your instance of Orange Logic works or looks. Examples of parameter changes include creating a new metadata field, changing the layout of an asset subtype, changing an asset’s action buttons, and replacing the site logo.
Changes to database objects are not limited to sessions and are visible to other users. Database objects include assets, groups, tags, and user accounts. Here are some examples of changes that all users will see (if they have the required privileges):
- Uploading a new asset.
- Renaming an asset.
- Creating a folder.
- Deleting a group.
- Creating a new tag.
- Creating a user account.