When this task executes, it opens the Open Debug panel that displays the data of different data stores and the communication logs at the application level. On a specific element, you can configure the “Open Debugger” task when you want to access and monitor the data of different data stores.
This task is specially configured for the software development purposes.
Steps to Configure
- On the Event Configuration page, find the Task panel.
- In the Task panel, search and find the Open Debugger task.
- Drag the Open Debugger task from the Task panel to the Execution panel.
- Under Open Debugger, a group of boxes appears.
- In the boxes, configure different properties as follows:
|Reference Name||In this box, enter the name of the task. Also the system generates a reference name by default that you can change.||Yes|
|Business Rule(Optional Step)||In this box, you can configure a business rule to determine the execution of the Open Debugger task. If the user’s action satisfies the condition in the business rule, the Open Debugger task is executed.|
To configure the business rule:
–> In the Business Rule box, click the application tree icon (), and the Business Rule panel opens.
–> In the Business Rule pane, click Create New to configure the new business rule.
After the Open Debugger task executes, it opens the Debug Screen page. On the Debug Screen page, you can access the different types of data that are typically stored in the JSON format in the user-defined and system-incorporated data stores. These data stores are briefly described as follows:
|Data Store Type||Description|
|Element Store||It is a system-defined data store. The Element Store contains the configuration details of all elements that are used in the application.|
|Entity Store||This data store contains data related to different types of entities. In the Vahana cloud?s ecosystem, the entity can be classified as follows:|
–> Business Entity
In the Vahana cloud system, the business entity specifies the core of the software application. The business entity stores all the business-related data in the application.
–> Temporary Entity
During the usage of the application, the temporary entity is used for calculation or computation purposes. The temporary entity exists till the application session lasts.
–> Transient Entity
In terms of life-cycle, the transient entity is not a permanent entity like a temporary entity, but the life-cycle of the transient entity exists beyond the application session. The transient entity exists even after the application session ends. The vDesigner tasks and events typically use the transient entity for the functional purposes.
|System Variables||System variables can be referred to as system related properties. The system variables store system-related information. The system-related information includes the followings:|
–> Platform name
–> Security version
–> Device model
–> Device make
–> O/S Version
–> IMEI number, etc
- After you configure the related properties, click Save to configure the Open Debugger task.