Set the Targeted JSON Pointer

using JSON Pointer..

ASTER::ACTION::JSON::Save the targeted JSON Pointer

Save the JSON Pointer as a target path in ASTER. The saved target can be used with specialized JSON commands corresponding to the target path.

The JSON Pointer typically requires specifying the path each time, but when using the same path repeatedly in loop processing, using the target path can contribute to processing efficiency by omitting the need to input the URI. The Targeted JSON Pointer can be used with “target-compatible commands.”

Targeted JSON Pointer: List of Compatible Commands

• JSON :: ACTION :: Batch Assignment for Oi Alt String[n]
• JSON :: ACTION :: Batch Assignment for Oi Alt Val[n]
• JSON :: ACTION :: Batch Assignment for Oi Flag[n]
• JSON :: ACTION :: Targeted Array :: Set the Val As Bool
• JSON :: ACTION :: Targeted Array :: push_back String
• JSON :: CONDITION :: EvD :: if targeted is Array
• JSON :: CONDITION :: EvD :: if targeted is Type of Bool & Val True
• JSON :: CONDITION :: EvD :: if targeted is type of Bool & Val False
• JSON :: EXPRESSION :: Targeted JSON Pointer :: Get As Number Type
• JSON :: EXPRESSION :: Targeted JSON Pointer :: Get Num of Total Array Elements

Parameter.1

Input of JSON Pointer

As an example of an actual JSON Object

{
    "test":"Example"
}

Specify a string with the key name “test” that is located directly under the root.

"/test"

Parameter.2

A Search Unique ID (search uID) is issued when setting a target.

This is a useful parameter when you want to perform different processing for each search unique ID.

When registering a target path, the validity of the JSON Pointer and the type judgment of the data type at the specified path are executed. If the data type is JSON array, the immediate execution condition “Tgt is an Array” is executed. In this immediate execution condition, search uID is used to identify the source of the event call.

1

By properly setting the search uID, you can distinguish between a different target path registration event executed at another time (search ID == 2) and the most recent event (Search uID == 1).

If you use the CF25 event line number as the search uID, it becomes easier to understand which line the immediate execution condition was set on, and the author recommends this.

Note

When calling immediate execution conditions, do not share the event row with other actions.

If you set a Targeted JSON Pointer, registering other actions in the event row may lead to execution conflicts and result in abnormal behavior.

In the sample image above, the action in Row 3 cannot be consolidated into Row 2.

When a Targeted JSON Pointer is registered, ASTER checks the data type at the specified path. If the data type is an array, the immediate execution condition “Tgt is an Array” is activated, and processing transitions from event row 3 to 4.

During the row transition, the event in Row 3 is not completely finished.

After the action in Row 4 is completed, the row transitions back to Row 3, and the action in Row 3 is finalized.

For processing that includes such immediate execution conditions, it is safer to use independent rows in CF25 event creation. This is almost identical to the standard feature of CF25 called “fastLoop” and equivalent in mechanism.