To link everything together in an application we need processing. This can be done using the logic layer of the builder. The business logic and rules are encapsulated in a series of actions which happen for example, when buttons are selected on various types that complete certain operations on other types. This is all brought together with ‘Actions’. Actions, whether standard or custom scripted, are essential tools for enabling us move around the system and process the data according to business rules which make up the purpose of the application. When we want to process data or move around the system – the data itself is not sufficient - we need an Action which is a bit of processing script that links forms, types and views together.
Once Actions have been created, they can be made accessible to a User from a variety of places within the application, which would include: Menus Tool Bars Access Bars Custom Action Buttons (Included on forms)
This is a Pengower storage reference number, which is a read only data item, which is used by Pengower’s technical staff to trace the storage of data objects in the system
Used to display the Action.
A description of the Action function or other design note
A representation of the action which is displayed in Menus, Toolbars, and Access bars.
Permitted User Types
Allows you to select which user types are allowed to use this action. If none are selected, it is available for all user types. If a user with a user type that is not permitted accesses this action, a message will appear saying 'The current user type is not allowed to execute this action or it is deprecated'
Not in use
When the box is ticked, a message will appear when the action is accessed saying 'The current user type is not allowed to execute this action or it is deprecated'
Selection of different standard actions that defines the action's function.
Action Parameters are used to define the context within which the Action is to be performed, such as the specific Types, Objects and Elements the Action is to be performed in relation too
There are two types of Actions: the platform enables us to create simple Actions without having to write any code at all – these are called Standard Actions. Alternatively, we can go in and write more sophisticated script using Pengower’s Action Script - these are Scripted Actions
The platform enables us to create simple Actions without having to write any code at all – these are called ‘Standard Actions’.
Examples of Standard Actions:
Some standard actions have more parameters than others and where parameters are not required then the placeholders will be grayed out.
The Origin Parameter has a number of options:
- Current Object – means execute the standard action (Eg. Copy) the Object that is Currently displayed in the workspace.
- Current Selection – means execute the standard action (Eg. Email) the currently selected List Items
- Value – means execute the standard action (Eg. Create) in relation to the Type of Data Object specified in the Value dialogue.
The Attribute Parameter has a number of options:
- Type – means the Type of Object to which the action is to be performed.
- Filter – Means the filter to which you wish to apply the action (Eg. Open/List Type “People” born before 1967)
- Field – The Particular field/element that you wish the Action to be performed on. (Display the Content field)
- NB - Entries into the Value field of the parameters dialogue are case sensitive.
The list of Standard Actions includes:
- New Object
- Open (List)
- Add Attribute
- Remove Attribute
If Standard Actions aren't able to fulfill our requirements we can go in and write more sophisticated script using Pengower’s Action ScriptScript. Scripted Actions can be deployed to run typical operations across data.
Within the Pengower Development platform (Application Builder) it is necessary to encode specific business rules to ensure that applications reflect and support real business processes. Pengower ActionScript is a simple scripting language developed to work with the Pengower Platform to deliver the required business logic.
The syntax for the script has been kept deliberately simple so that the language can be learnt and mastered without a significant background in software development or IT.
Scripting is used when basic Action definitions don’t provide sufficient flexibility both in terms of functionality and in terms of visual output. Scripts are written as part of an Action definition, i.e. when the Action is called by the end user the associated script is executed.
The Pengower scripting engine works in an interpreted mode – i.e. the script re-read and re-processed each time it is accessed.
This manual outlines the basic syntax and structures used in Pengower Action Script.
Where Actions are run from
Actions can be triggered from different points within the application. Scripted or Standard Action can be incorporated into the builder's Menus, Toolbars and Access Bars. In fact these structures are little more than collections of such Actions.
There are four other important places where actions can be run from: Views, Forms, Types and Groups. When they are run from these locations, the Actions are likely to be scripted because they usually require some level of data processing.
- Launch Actions
- Form processing
Scripted or Standard Action can be incorporated into the builder's Menus, Toolbars and Access bars. In fact these structures are little more than collections of such Actions.
There are four other important places where actions can be run from: Views, Custom Forms, Types and Groups. When they are run from these locations, the Actions are likely to be scripted because they usually require some level of data processing.
Creating and Editing Actions
You can visit our tutorial on How to create a Standard Action to know more on how you can create and edit Actions.
You can see how Actions are created and used in this video below: