Posted: Sun Sep 15, 2002 4:29 am Post subject: RFI for MQWorkflow
Newbie
Joined: 15 Sep 2002 Posts: 1
Hi,
I'm currently responding to an RFI for a bank client which is interested in getting MQ Workflow. I hope you can help me in some of their requirements...
Will MQWorkflow meet this requirement without any programming effort and How? Or with how much programming effort and how?
Process Definition:
1. Capability of MQ Workflow to define checklist of document requirements for a process.
2. Capability of MQ Workflow to validate transaction versus document requirements checklist.
Data Capture:
1. Capability of providing data entry selection of valid field values through drop down list.
Process Management:
Work Initiation and Routing
1. Have a business calendar facility that supports automatic initiation of a process based on a user pre-defined date and time schedule
2. Capability to compare cycle time versus standard turn-around time (can I use Holosofsx?)
Process Monitoring and Notification:
1. Capability to send notifications via SMS.
2. Capability to send notification to processor regarding work in queue (worklist..)
Queue Management (worklist mgmt)
1. Capability to automatically assign activity to a processor with the least load
2. Capability to automatically re-assign pending activity to another processor if it is not completed within pre-set standard turn-around time
3. Capability for processor to reject or delegate an activity to another processor
4. Capability for manager to change and assign the priority level of a transaction overriding the default queuing rule (such as first in - first out)
5. Capability for manager to change sequence of activities overriding the default process flow for a specific transaction
6. Capability for manager to re-assign pending activity to another processor manually
7. Capability for manager to rollback a transaction to its previous state or undo a transaction entirely
Security:
1. Ability to secure access to the system utilizing encrypted passwords and logon IDs
2. Ability to link to the bank's security system ACFS -Mainframe
3. Ability to support SSL if web-enabled
4. Ability to copy security profiles
5. Ability to disable/expire the logon ID after specified number of unsuccessful logon attempts
6. Ability to disable/expire the logon ID after specified number of days inactivity
7. Should disallow simultaneous use of logon IDs
Version Management
1. Ease of creating new versions due to new / modified data fields
2. Ease of creating new versions due to new / modified processes
3. Capability to handle pending transactions when transitioning from current workflow version to a new version
I do not have any implementation experience on MQ Workflow. I learned about this product in a bootcamp I attended last year. I hope you can help me respond to the above requirements and hopefully we can close the deal and I'll have my 1st implem exp.
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
It's a long list....
Quote:
Data Capture:
1. Capability of providing data entry selection of valid field values through drop down list.
This can be done and it is upto you how you build your user interface.
Quote:
Process Management:
Work Initiation and Routing
1. Have a business calendar facility that supports automatic initiation of a process based on a user pre-defined date and time schedule
This can be one and it's an inherent MQ Workflow feature. No effort is required.
Quote:
Process Monitoring and Notification:
1. Capability to send notifications via SMS.
2. Capability to send notification to processor regarding work in queue (worklist..)
It has capability to send notifications but for SMS I guess you have to use MQ Everyplace. I am not sure if this can be done.
No. 2 can be done programatically (like sending an e-mail).
Quote:
Security:
1. Ability to secure access to the system utilizing encrypted passwords and logon IDs
2. Ability to link to the bank's security system ACFS -Mainframe
3. Ability to support SSL if web-enabled
4. Ability to copy security profiles
5. Ability to disable/expire the logon ID after specified number of unsuccessful logon attempts
6. Ability to disable/expire the logon ID after specified number of days inactivity
7. Should disallow simultaneous use of logon IDs
1, 5, 6 can be implemeted uisng the authentication exit. 7 is a feature of MQ Workflow.
Quote:
Version Management
MQ Workflow has a long way to go in terms of version management.
Hope I have answered a few of your questions. You should be getting more better replies from the "masters" of this forum.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum