Tasks let you monitor when specific events occur in a Flow.
To track tasks in a Flow, use a Complete Task Node.
Once the Node is triggered,
the task is recorded in the Analytics database and can be monitored in the Contact Profile,
viewed in Insights reports and explorers, and accessed through the OData endpoint for further analysis.
For more information, read the Complete Task Node article.
Compatibility Alias to profile.tasks
In the Profile object, profile.goals has been renamed to profile.tasks.
To ensure your existing code still works in Flows, profile.goals now functions as a compatibility alias that points to profile.tasks. This means you can still use profile.goals. Its value is stored in the profile.tasks object. Accessing profile.goals provides the value from profile.tasks, for example:
- When using the
{{ profile.goals }}or{{ cp.goals }}CognigyScript expressions. - In Code Nodes, Extensions, and Functions.
profile.goals alias is available for existing implementations to maintain continuity. However, for new Flows, use the new profile.tasks naming convention in your CognigyScript expressions and code. This approach ensures that your Flows comply with the latest platform standards and best practices.
Restrictions of the Alias
This compatibility alias forprofile.goals isn’t a standard property of the Profile object.
This alias limits how you can use or inspect it:
- Property Listing –
profile.goalsdoesn’t appear when you list the object’s properties, for example, when usingObject.keys(profile). - JSON Serialization –
profile.goalsdoesn’t appear when you turn the Profile object into JSON, for example, when usingJSON.stringify(profile).