You can use placeholders in your script to reference the target asset and the current user. To add placeholders, enter an opening bracket ([) and select a placeholder from the list.

Asset information

Most asset placeholders use the format Document.[Field name]. Some of the most common placeholders for the Core fields of a target asset include:

• Document.Title
• Document.CaptionLong (the Description field)
• Document.Copyright
• Document.FileCreateDate
• Document.FileEditDate
• Document.FileImportDate
• Document.FileSize
• Document.EmbargoDate (the Embargo Date field)
• Document.Identifier (the unique ID)
• Document.Purpose (the Visibility Class)
• Document.IIIFResourceType (the IIIF Resource Type field)
• Document.Lockdown (Assets in lockdown cannot be shared, and all existing shares are revoked.)
• Document.OriginalFileName
• Document.WorkflowStatus
• Document.DocSubType (the asset subtype)

Additional asset information placeholders you might find useful include:

• Document.TitleWithFallback (the assets title or, if there is none, the asset’s original file name)
• Document.Embargo (a boolean value indicating whether the asset is under embargo)
• Document.Keywords (the asset’s tags)
• Document.RecordID (the asset’s Record ID)
• Document.EditDate (the Last Modified date)

📙

Feature documentation

Orange Logic users with a Link account can go to the following articles to learn more about these topics:

• Core fields
• Embargoed assets
• Visibility Classes
• IIIF support in Orange Logic
• Asset subtypes
• Tags

User information

Some of the most common placeholders for user information are listed below. These placeholders pull information from the account of the user who triggered the automation.

For example, when a user clicks a button or saves an asset to trigger an automation, the Sender.CoreField.First_Name placeholder pulls in the value of the First name field in the user’s contact record.

• Sender.CoreField.First_Name
• Sender.CoreField.Last_Name
• Sender.CoreField.OrganisationName
• Sender.CoreField.Contact_type (the type of account, such as Staff, Source, etc.)
• Sender.CoreField.Department
• Sender.CoreField.DisplayName
• Sender.CoreField.Identifier
• Sender.CoreField.LoginID
• Sender.CoreField.MustResetPassword
• Sender.CoreField.CreateDate
• Sender.CoreField.EditDate
• Sender.CoreField.EditLocation
• Sender.RecordID (the encrypted ID of the user’s account)

📙

Feature documentation

Orange Logic users with a Link account can go to the following articles to learn more about these topics:

• Accounts
• Account types

Workflow variables

You can add variables to workflows to make workflows flexible, dynamic, and personalized. Variables store and pass values between steps in a workflow. You can set variables on all workflow elements (triggers, actions, statuses, decisions, etc.). Then, you can reference variables in later workflow elements, including integrations built with the Call external API action.

To add a workflow variable to your script, enter an opening bracket inside single or double quotation marks ( “[“ ) and type "Variable" to list that workflow’s existing variables. Select a variable to add it to your script. Alternatively, you can type [Variables.variable name] to add the variable. Variable names are case insensitive and can include spaces.

Configure the script’s sample response in the bottom window as a JSON object. Then, use the Utils.SetScriptOutput function to set the response in the script template.

You can also designate the script’s response as a workflow variable with this syntax: var response =.

The script sample below imports an asset and its metadata to the Orange Logic platform. The asset’s title is “Product photo,” and its description is the AI agent’s confidence score, which is a variable pulled from the workflow. The response is configured to list the asset’s title and the success status. The response will be available as a variable in the Workflow Design Tool.

Utils.ImportFromThirdParty(
    {
        DownloadURL: 'https://mangovations.orangelogic.com/AssetLink/4ry6b3133j753w1a03nh3t8jpwspyx17.JPG'
	FolderID: '2Y8TWAFUPL3'
	SingleValueMetadata: { "Title": "Product photo", "Description": "[Variables.Agent confidence score]" }
    },
    // Success callback function
    function (_sResp) {
        var oResp = JSON.parse(_sResp);

        Utils.SetScriptOutput(oResp);

        Log.Warn('Executed successfully: ' + _sResp);
    };
//Failure callback function
function (_sResp) {
    Log.Warn('Execution failed: ' + _sResp);
}
)

ℹ️

Note

• Workflow variables are available beginning in Orange Logic Ottawa.
• Orange Logic users with a Link account can go to the Workflow variables article to learn more.