Page History
...
In your Logic (attribute value expressions, Decision tables, Business rules, Reusable Expressions, etc.), you always reason starting from "self" (in other words, the instance that you are setting a value for).
...
- Yourself (in the above example, if the attribute Customer.Age refers to Customer.BirthDate, then this is always the same Customer instance)
- Instances that you have a Relation with (whether these are active or not)
- Singletons (these are always active)
- Static instances
- And you can make use of Collection functions to access other instances
...
- Instances created with the Service call Service call type: AQ_Instance_Create are immediately active
- Existing instances can be activated with Service call type: AQ_ActivateInstance
- A repeat Flow can be used. This flow is run once for each specified instance. Within each iteration of the flow, the next instance is activated
...
- Instances that an active instance has a Relation with (whether these are active or not)
- Singletons (these are always active)
- Static instances
- And you can make use of Collection functions to access other instances
Active instances - on a page
Within a Page, it is possible to control which instances are active in several ways:
- New instances can be created for 1:1 Relations by adding that Relation to the page
- A Repeat container can be used. This container is displayed once for each specified instance. Within each iteration of the container, the next instance is activated
- The Container type: AQ_InstanceList can be used to display (specified) instances of a particular entity.
...
- Instances that are already active in the flow (see above)
- Instances that an active instance has a Relation with (whether these are active or not) by adding that Relation to the page
- Singletons (these are always active)
...
| Anchor | ||||
|---|---|---|---|---|
|
Several Service calls can be used to manage instances:
...
Overview
Content Tools