588 views

Workflow Engine Ordering and Data

 

Goal
Some practice in understanding how data is transformed in the process of a Glide Record transaction.

 

Practicing engine ordering

The following exercises are to become familiar with the transformation of data as it moves through the Glide Transaction.

In the following tables there are a series of Business Rules and Workflows presumed. Each one simply does a modification to the same field throughout the Glide Transaction.

The script in each is very simple:  current.desc += ‘some value’;

For example:

current.desc += ‘K14’;     // the value of current.desc = K14

current.desc += ‘-WF 301’; // the value of current.desc = K14-WF 301

and so on.

  1. Walk through following scenario:



    QUESTION: What is the value of current.desc in the database at the end of the Glide Transaction?

  2. Walk through the following scenario:



    QUESTION: What is the value of current.desc in the database at the end of the Glide Transaction?

    QUESTION: Will the value of current.desc ever equal BLB-WFDefault-BHA in the database? Why or Why not?

  3. Walk through the following scenario:



    QUESTION: What is the value of current.desc in the database at the end of this Glide Transaction?

    QUESTION: How many updates were performed to get to that place?

Article Information

Last Updated:2016-05-13 13:11:22
Published:2014-05-16