Apologies for this 'noob' question, but I'm slowly getting to grips with Bizagi, and this I believe to be a fundamental 'process' type, and resolving it will clarify many different types of process instances. (I'm in a company that currently has Bizagi employees working on-site, but, I do not wish to unfairly impinge on their project time). Imagine that I wish to authenticate whether a network user is authorised to use this particular Bizagi application. 'Network user' = network logon name and these are stored within the Bizagi data-store against department user names and other information. So, this user is NOT stored within the 'authorised user' data-store, but IS stored within the organisation structure data-store - under a specific department, and so is the 'lead' of this department (usage of this app can only be authorised by the department lead). However, this user may have ALREADY attempted to use the app, and an authorisation task has ALREADY been assigned to the users 'lead' which has not yet been completed. In my view, this authentication process (for this particular user) is still 'outstanding', and can be 'trapped' at the start of this process (so that further authentication checks are not activated unnecessarily AND, a further request to the 'lead' will not be unnecessarily issued). The user has simply tried to run the app again - before the 'lead' has completed the authorisation process. I'm guessing so-far that the 'lead authorisation' task is a 'TRANSACTIONAL' sub-process, which would 'hold the process open' until completed. Is the 'transactional sub-process' the correct solution for this type of process? Hope I've been clear enough about the process intention. Regards, Darrylle
↧
