Answer:
► Short lock. This is the standard lock normally set
by the TIBCO iProcess Workspace. A short lock is removed
when a user keeps or releases a work item. In the event
that short locks are left behind because, for example, the
iProcess Workspace crashed, the only way to remove the
short lock is to re-start the iProcess Engine or use the
► Long lock. A lock that is persistent and can only
be removed using sal_llock_frm_init() by the user holding
the lock. Long locks are not normally used by TIBCO
iProcess Workspace, but may be set by SAL SDK programs or
the TIBCO iProcess Objects Client. Re-starting the iProcess
Engine has no effect on long locks, so a work item locked
in this way remains inaccessible to every iProcess user
until it is manually unlocked.
by the TIBCO iProcess Workspace. A short lock is removed
when a user keeps or releases a work item. In the event
that short locks are left behind because, for example, the
iProcess Workspace crashed, the only way to remove the
short lock is to re-start the iProcess Engine or use the
► Long lock. A lock that is persistent and can only
be removed using sal_llock_frm_init() by the user holding
the lock. Long locks are not normally used by TIBCO
iProcess Workspace, but may be set by SAL SDK programs or
the TIBCO iProcess Objects Client. Re-starting the iProcess
Engine has no effect on long locks, so a work item locked
in this way remains inaccessible to every iProcess user
until it is manually unlocked.
| Previous Question | Next Question |
| Where can you see the description of the error when a Case is terminated abnormally? | What is Business Process Management (BPM)? |