1

ECTRN_CHECK_IN_LOCATION

Field Updated (After)

Copies the coordinates of the Location ID and assigns to the Asset ID upon Check-In

2

ECAI_ASSET_LONGITUDE/LATITUDE tca

Trackor Created (After)

Upon Asset Item creation, this rule auto-populates the coordinates based on the Home Location's (parent) coordinates.  

3

ECAI_ASSET_LONGITUDE/LATITUDE cfu

Field Updated (After)

Assigns the coordinates of the Transaction ID to the Asset upon an update upon check-out.
OR
Updates the coordinates of the Asset to reflect the Home Location upon check-in.

4

Assets rollup

Field Updated (After)

Identifies Transaction details to the Asset level including Return Dates and other Flag fields such as Repair Needed and Out of Service Fields.

5

ECAI_ASSET_NAME ECAI_ASSET_TYPE

Field Updated (After)

Copies the Name and Type field values of the Master Equipment Trackor and copies Asset Records that reflect this Equipment assignment. This rule ensures updates at the Master Equipment level cascade down and update Asset Items.

6

ECAI_MAINTENANCE_REQUIRED cfu

Field Updated (After)

Identifies if Maintenance is required soon based on set schedule.

7

ECTRN_STATUS Checked In

Field Updated (After)

When the EC-TRN:Status field is set to Check-In Complete, then create a new Transaction Record.

8

New Transaction on new Asset

Trackor Created (After)

Creates a child related Transaction record upon the creation of an Asset ID.

9

ECAI_ASSIGNED_TO

Field Updated (After)

Copies the Assigned To value at the Transaction level and copies the value up to the Assignee record that reflects the Assigned user.

1

Navigate to Dev Center > Application Process Management > Rules.

The screen will open the Rules page.

2

As an Admin User, you can create new rules or manage/modify existing rules.

For our Case Study, let’s create a new rule. Press Add.

Rule: Name the rule. Typically you should create a name that is reminiscent of the functionality.

Rule Class: Select “PL/SQL” as most rules created will use this dropdown choice.

Rule Type: Select “Trackor Created (After)” – This is our selection since our goal is for this rule to execute after a Trackor Record is created (aka Added) in the Asset Items Trackor page.

Rule Description: Enter details about your new rule. What does it do and how is it triggered to run? What fields are updated as a result of the rule functionality?

Press Apply to create your rule and continue to configure.

3

4

After pressing Apply, a system generated Rule ID number will be assigned. Additional Tabs will now be visible where we can further update the rule in order for it to run.

5

• Click on the ID Numbers Tab.

• Press the Add.

• In the new window, select the Trackor Type for your rule. Press OK.

  • The selected Trackor Type is where the new rule triggers.

• Click on the PL/SQL tab. Write or paste in custom SQL to represent the logic of your rule.

• Press Apply to save your changes.

• Click on the General tab. With your rule now configured including an ID Number and PL/SQL, click the Enabled box, then OK.

Your new rule has been added and enabled in the system.

6

Let’s test the new rule!

• Navigate to the Asset Items page.

• Press Add to create a new Asset ID Trackor Record.

• Complete the Fields to create your new Asset Item Trackor Record and press Apply.

• Notice our new Rule automatically created the child Transaction Trackor Record.

As new Asset IDs are created, the rule will always create an initial Transaction record.

1

From the Rules page, press Add, just like we did in the previous Example 1.

• Create your Rule Name

• Rule Class = “PL-SQL”

• Rule Type = “Field Updated (After)”

  • This rule will be triggered by a Field value being updated. In this case the EC-TRN:Status field.

2

Navigate to the ID Numbers Tab, which is the rule trigger.

• Click Add and select EC-TRN:Status (aka ECTRN_STATUS).

3

Navigate to the PL/SQL Tab.

• Enter your PL/SQL code.

• Press Apply.

4

Navigate to the General Tab.

• Check Enabled?

• Press OK to save the Rule.

5

Let’s test the new Rule!

• Navigate to the Asset ID and click on the record. Then click on the Transaction Tab.

• Click on the existing Transaction ID record.

• Update the TRN:Status field to “Checked In (Complete)”.

• Press OK to save and close the window.

• Refresh the Grid on the Transaction Tab by clicking on the Quick Search icon.

• The new Rule has automatically created a new “Transaction” record.

In the video, we perform two transactions resulting in the creation of two new records.

NOTE: As we continue developing the “Equipment Checkout” system, we will add additional Rules and Automations to support our desired business logic. It’s important to consider the enabled rules in place when adding any additional Rules and Automations.

1

Navigate to Dev Center > Application Process Management > Automation.

The screen will open the Automation page.

2

• Click Add.

• Enter a unique Automation Name.

• Select the Trackor Type. This selection will be where Triggers happen.

• Description: Enter details about the automation. What does it do and how is it triggered to run? What fields are updated as a result of the rule functionality?

• Click Apply. This will save your progress and cause additional Tabs to be visible to add parameters to the Automation.

3

• Navigate to the Trigger Tab.

• Select the ellipsis next to Delete and select the type of Trigger to add.

• Select the Trigger Field and then OK.

• When all Triggers are set click Apply.

For this Automation, we have three Field Updated (After) and one Trackor Created (After) triggers.

4

• Navigate to Filter Action Tab.

• Click Add.

• Select the Action Type.

• Order Number (optional) sets the order in which the automation checks each parameter. Important when using Stop on Filter Match.

• Target Field is the field that will be updated.

• Action Mode is either Constant Value or Formula (selected when the desired value may vary).

• Depending on Action Mode, either select the Target Value or Formula.

• Click OK.

5

• Navigate back to the General Info Tab.

• Check the boxes for Enabled and Stop on Filter Match, which will stop the automation when one of the conditions are met, based on the order.

• Click OK.

The automation is complete.

6

Watch the Transaction Status update based on the automation parameters.

1

In order to sum the total number of returned (check in complete) assets, we need a field on each Transaction that displays either a 0 or 1 (when completed) and a Field that displays the sum on the Assignee record.

Follow instructions here on how to add a field.

For the example, we will add:

• Transaction Trackor Type named EC-TRN:Asset Checked In;

• Assignee Trackor Type named EC-AT:Assets Returned

• Both are set to Read Only, since they will be populated by Automations.

2

Next, we add an Automation that populates EC-TRN:Asset Checked In field with a 0 or 1.

This follows the same process as the Automations example above, with different Triggers and Filters. See Rollup Transaction Automation video.

3

Then, we add another Automation that sums the child Transaction fields with a 1 into the Assignee Field EC-AT:Assets Returned.

The process repeats, building on the Transaction level Field and Automation from the last step, as it is used as the Trigger in this Automation. Additionally, this time we use a Formula and not a Constant Value on the Filter.

See Rollup Assignee Automation video.

4

The Rollup is complete!

In the video, you can see that there is now a value in the field that correlates with the number of completed Transactions for the Assignee.

Look at Field History > Call Stack to see the flow of the field update. First there is a manual update to check out, then all three Automations trigger - one updates the Transaction Status, one updates the EC-TRN:Asset Checked In to 1, and one sums up all the Transactions with a 1.

1

Navigate to Dev Center > Build Applications > Notifications.

The screen will open the Notifications page.

2

Press Add to open a create new Notification window.

Based on steps detailed in the Video of the below section, we will populate fields and make updates in order to create our new Global Notification.

1

Create a Name for your Notification

2

Set your Scope to “Global”

3

Check boxes for:

• Auto Activate

• Html

• Forced Subscription

4

Notification Type = “Trackor Updated”

5

Primary Trackor Type = “Transaction”

6

Create a Subject using static text and values from the Attributes field selections.

• The Attributes dropdown allows you to select field attributes from a Trackor Type along with standard Notification values that you can add to your Subject or Message.

7

Create a Message using static text and values from the Attributes fields.

• Include HTML code to manage formatting for your message content.

Note: It might help to increase the size of this window while working in it.

8

Press Apply to save, then continue.

9

Click on the Filter to define the conditions of which records will be triggered by the Notification.

Set your desired parameters and press OK.

10

Select the Field(s) that will trigger the Notification by pressing the “+” icon.

11

Press OK after selecting.

12

Press Apply on the Notification to save.

13

Click on the User Filter to define which users will receive an e-mail.

• In this case, we will use default SQL to send to the user who triggers the Notification.

• In the next steps, we will add additional code to further select recipients based on configured fields.

14

Click on Select Recipients using SQL.

• Enter SQL to reflect the Assignee field that contains the E-mail address of the person who checked out the Asset, EC-TRN:Email Address in this case.

15

Check the Enable box to make the Notification active.

16

Press OK to save and close the window. It is now enabled and assigned to Admin Users.

Further assignments can be completed by assigning to Security Roles, reviewed in the Security section.

17

As showcased in our User Experience Demo, video, recipients of the Notification will receive an E-Mail in HTML format detailing information about the Asset Item that is checked out and assigned to them.

1

Navigate to Dev Center > Design Applications > Hide Tab Elements. Click Add on the Hide Tab Elements page.

2

Select the Trackor Type, then the Applet, then the Tab.

For the example, we select EC_Transaction, Transaction, then General Info.

3

Now select the field that will be the trigger field.

For the example, we select TRN:Status.

Since Status is a Drop-Down, we also need to select the trigger value, Ready for Check Out in this case.

4

Now the General Info Tab is displayed and you will select the fields that should be hidden when the trigger is met.

In the example, we will hide everything below the line at the bottom of the CHECK OUT section (including the line itself.) Hold CTRL to select multiple Fields.

5

Click Apply to save and confirm the correct fields are selected. Click OK to exit and see the new item on the Hide Tab Elements list.

6

Because we have two more scenarios where we wish to hide Fields, we will Add two more Hide Tab Elements with different triggers.

When the Status is Checked Out, hide the CHECK OUT section.

When the Status is Out of Service, hide everything because the Asset cannot be checked in or out until its back in service.

7

Now when we go to the Transactions Trackor Record, different Fields will be hidden depending on the value in TRN:Status.

See the screenshots to see how the same Tab in the app looks in each case.