Package com.sas.metadata.remote

Interface SyncStep

All Superinterfaces:
AbstractTransformation, CMetadata, MdObjectBase, MdObjectBaseUtil, MdObjectBaseXML, PrimaryType, Remote, Root, TransformationStep
public interface SyncStep extends TransformationStep
The SyncStep is used to define a part of workflow. This step does not represent a process step, but instead a point of synchronization to help define complex flow algorithms. Valid roles for this type are: AND, OR, EVENTWAIT, or CASE

An AND SyncStep would have multiple PredecessorDependencies that all must occur before the SuccessorDependencies are activated.

An OR SyncStep would have multiple PredecessorDependencies. Any one of these would have to occur before the SuccessorDependencies are activated.

An EVENTWAIT SyncStep is activated by TriggeringEvents.

A CASE SyncStep signals the start of case logic.

Attributes of SyncStep are:

Associations of SyncStep are:

Usage

To create an instance of this SyncStep, use the factory create methods.
Example: create a SyncStep with name "SyncStep_Object", in repository "AAAAAAAA".
 // create a store to contain your objects for this change. If you do not have an existing object
 // or store to use.  You may obtain the store from another object by using Object.getObjectStore().
 MdFactory factory; //where "factory" is a valid MdFactory instance
 MdObjectStore objectStore = factory.createObjectStore();
 SyncStep myObject = (SyncStep) factory.createComplexMetadataObject(objectStore, "SyncStep_Object", MetadataObjects.SYNCSTEP, "AAAAAAAA");
 myObject.updateMetadataAll();  // Write object to server
 objectStore.dispose();  // dispose of the object store if it is no longer needed

Behavior

  • Attributes and associations for this object can be retrieved by using the methods in MdOMIUtil.
  • When changes are made to the object, either by setting an attribute or adding objects to a particular association, they can be persisted to the metadata server with the updateMetadataAll method.
  • If an object needs to be deleted, the delete method can be used. This will flag the object as being deleted on the client, and will require an update call to persist the change to the server.

Dependencies

This class depends on objects being contained in an MdObjectStore. Object stores should be disposed of when they are no longer needed as this will help clean up memory. Disposing an object store will dispose of all objects contained within that store.

Since:
9.0