Transaction Template

TransactionTemplateImg01

The purpose of Template node is to define a structure template which will be instanciated for some instance's transactions. When we create a new transaction and then apply WorkWithPlus pattern, the instance will be generated based on some of these templates.

As we can appreciate, Template node has a very similar structure to any particular transaction's pattern instance. Many nodes are exactly the same to the ones presented in transaction's pattern instances, but others just represent a layout within the instance's structure in which particular nodes will be placed.

For example 'Variable' node or 'Text block' node are the same in both cases (instance template and particular instance) but 'Attributes' node does not exist in particular instances because it represents the layout in instance where all the transaction's attributes will be placed. In other words, the purpose of 'Attributes' node is that pattern could know where to put transaction's attrubutes at the moment of generating it by default. The nodes 'Subor levels position', 'Orders', 'Filters', 'Fixed Attributes', 'Tabs Position' are analogous to 'Attributes' as they represent a location but not some behaviour.

Below you can visualize examples of the differents styles of Selections that you have in the Transaction Templates:

TransactionTemplateImg04

TransactionTemplateImg05

TransactionTemplateImg06

Transaction Template node has the following properties:

Category Property  
Settings Preview Preview Transaction TransactionTemplateImg02
Update Intances Process Delete Nodes Action
Deleted Attributes Action
Generate Log

Properties Of Category Settings Preview:


Preview Transaction:

Specifies which transaction is going to be used as an example at the moment of visualizing a preview of any of the intance generation template objects in any templates. This objects can be Transaction, Selection, View or any of the Tabs, Association and Association Selection.

For example, if we set this property as 'Company' (Company transaction), and execute Preview action on the Transaction object, the following is shown:

TransactionTemplateImg03

If you want to read more information about Preview, follow this link: Preview

Properties Of Category Update Instance Process:

Delete nodes action:

Specifies the behavior that will have the pattern in the Update Instances process when some nodes were deleted from a transaction. The values are:

  • 'Delete' will delete that attribute from all instances automatically
  • 'Ask User' will ask the user if he wants to delete it or not, for every object of all the instances.
  • 'Ask user if updating only one instance: will ask the user if he wants to delete it or not, only when you run the Update Instance process to one instance. Otherwise, it will delete all the nodes that were deleted from the default instance.

Delete attribute action:

Specifies the behavior that will have the pattern in the Update Instances process when some attribute was deleted from a transaction. The values are: 'Delete' that will delete that attribute from all instances automatically, or 'Ask User' will ask user if he wants to delete it or not, for every object of all the instances.

Generate log:

Specifies whether to generate logs about the Update Instances process or not. If True it will generate a csv file with all the information.


Event Blocks and Variables 

In every object template within the Transaction Templates (Transaction, Selection, Prompt, etc.) you can add Event/Sub Blocks and Variables. This is detailed in the following link: Event Blocks and Variables