OS lock types

4. Locking granularity

A. Input Parent workflow problem files (level 1 Data unit lock). The highest level of locking occurs when an input parent Workflow profile is locked. The workflow engine will force all data cells for the entities assigned to the input parent to be locked. This is accomplished by locking the input parent Workflow profile as well as all of its input child workflow profiles regardless of origin member binding or Workflow Channel assignment. B. Input child workflow profile (origin lock) OneStream uses a predefined relationship between the three types of input child workflow profiles and a static Dimension called the origin dimension to control and lock the three basic channels of input for an entity. This relationship provides the ability to control and lock data entry processes and associated data cells by binding the workflow profile input child types to origin dimension members. C. Input child workflow profile (workflow channel lock) Through the use of workflow channels assigned to input child workflow profiles and associated with accounts or user defined members, it is possible to provide very detailed locking granularity within a given origin number.

1. Explicit locks

An explicit Entity data lock is created when a workflow unit is locked there for locking it is assigned Entity(s) for the scenario in time associated with the workflow unit

2. Implicit locks

And implicit entity data lock is created when a workflow unit's Workflow has been certified. Implicit locks are created in order to ensure once a higher level workflow unit is certified, the underlying entity data cannot be changed. Implicit locks can be cleared by un-certifying the parent workflow unit

3. Workflow only locks

If a workflow unit is locked and the workflow profile does not have assigned entities, all workflow processing is blocked, but there are no entity largest placed.