Describe the integrations supported by Y/N your workflow engine with the externalized workflow engines of other systems Describe the API’s and protocols that your Y/N workflow engine supports Describe any specific technologies that your solution supports; e.g. specific browsers, etc. Support for request-driven workflow, Y/N initiated by administrator or authorized user action Support for event-driven workflow, Y/N initiated by change to information in authoritative source systems Support for event-driven account Y/N (i.e., not deletion) with or without workflow approval Support for request-driven account Y/N (i.e., not deletion) with or without workflow approval Support both workflow for disabling and Y/N deletion of accounts in separate steps (e.g., configured 30-day period’ ‘grace between deactivation and deletion) Support event-driven account re-activation Y/N with or without workflow approval Support request-driven account Y/N with or without workflow approval Support removal of accounts from target Y/N systems Support removal of accounts from target Y/N system groups upon deletion of user account Support removal of user accounts and Y/N user ID (person object) from identity management system upon deletion, with notification or pending workflow approval Support the triggering of a workflow that Y/N identifies all non-person (“generic”) accounts by a user being ‘owned’ removed from the identity management system, in order for an administrator to the accounts to new owners if necessary
Describe the integrations supported by your workflow engine with the externalized workflow engines of other systems Y/N Describe the API’s and protocols that your workflow engine supports Y/N Describe any specific technologies that your solution supports; e.g. specific browsers, etc. Support for request-driven workflow, initiated by administrator or authorized user action Y/N Support for event-driven workflow, initiated by change to information in authoritative source systems Y/N Support for event-driven account (i.e., not deletion) with or without workflow approval Y/N Support for request-driven account (i.e., not deletion) with or without workflow approval Y/N Support both workflow for disabling and deletion of accounts in separate steps (e.g., configured 30-day ‘grace period’ between deactivation and deletion) Y/N Support event-driven account re-activation with or without workflow approval Y/N Support request-driven account with or without workflow approval Y/N Support removal of accounts from target systems Y/N Support removal of accounts from target system groups upon deletion of user account Y/N Support removal of user accounts and user ID (person object) from identity management system upon deletion, with notification or pending workflow approval Y/N Support the triggering of a workflow that identifies all non-person (“generic”) accounts ‘owned’ by a user being removed from the identity management system, in order for an administrator to the accounts to new owners if necessary Y/N