support@everysk.com | Back to Everysk »

Articles in this section

Compliance Generator

The Compliance Generator worker validates whether a datastore follows user given conditions and rules. After the execution, the Compliance Generator worker generates a detailed compliance report which can be used in the compliance widgets.

mceclip0.png

Parameters

The Datastore Merge worker must receive specific parameters in order to execute properly. When parameters are not set correctly it may cause the worker to not work as expected.

 

1. Conditions

Handle the conditions by which the datastore will be validated. You can add more than one condition and group these conditions.

mceclip3.png

1.1 Add condition

When selecting the Add Condition button more fields are exposed, enabling the user to configure this condition. 

mceclip4.png

 

1.1.2 Property

Set the property which will be validated. You can pass such a property in two ways: 1) Pass the property using Upstream Data variant, or 2) expanding the Property field to explore a datastore.

 

Pass the property using Upstream Data variant

Set the Property value using Upstream Data variant.

mceclip0.png

Expanding the property field for data exploration

mceclip11.png

 mceclip12.pngmceclip13.png

mceclip15.png

                    mceclip17.pngmceclip20.png

1.1.2.1 Datastore

Select the datastore using Fixed Datastore, Get Latest, Get List or Upstream Data variants.

1.1.2.2 Date Range

When selecting a datastore using Get Latest or Get List variants, the Date Range field will be enabled to use in the exploration. It has the following options of date range: Custom Range, Last N Periods, Period To Date (Start), Period To Date(End) and Single Date.

mceclip1.png

1.1.2.3 Filters

You can set filters inside the exploration and separate them in groups to meet specific conditions inside of it. 

mceclip3.png

1.1.2.3.1 Filter By

Select the datastore property which will applied to the filter using Fixed Value variant.

1.1.2.3.2 Operator

Select the operator to be used in the condition statement using Fixed Value variant.   

mceclip4.png

1.1.2.3.3 Value

Set value to be compared using Fixed String variant.

1.1.2.1 Property

Select the datastore property using Fixed Value variant;

1.1.2.1 Format

Select the property format using Fixed Value variant.

1.1.2.1 Aggregated By

Select the exploration aggregation type using Fixed Value variant.

 

1.1.3 Property Label

Set the property label using Fixed String or Upstream Data variants.

1.1.4 Property Format

Set the property format using Fixed Value or Upstream Data variants.

mceclip5.png

1.1.5 Decimal Points

Set decimal points using Fixed Number or Upstream Data variants

1.1.6 Operator

mceclip6.png

1.1.7 List Operator

Set the list operator conditional using Fixed Value variant.

mceclip7.png

1.1.8 Value

Set the condition value using Fixed Value or Upstream Data variants

mceclip8.png

 

 

Result

Once the worker finishes it's executions succesfully, it will return a result object containing the retrieved result(s) to the workflow, which can be used by upstream workers. Below you can see an example of the Compliance Generator's result object hierarchy. You can check the Output Types article to learn more about result objects types.

  • Result (boolean)
  • Detailed Result (object)