Mobile workflow developers request your feedback - please speak up!

[Former Member]

Hello, The mobile development group is looking at some additional ideas for workflow on mobile devices and they have the following questions for you:

Item 1:

If you have to choose only one, what would be more important for you in case of a mobile application for approvals when you launch the application or bring it back from background after half an hour:

A) See the list of work items as fast as possible, so you can immediately try to start working even if some of the items might be out-of-date and there is some chance that you run into an error.

B) See an up-to-date list of work items and wait a bit more (2-4 seconds) for it.

Item 2:

For user decisions in the inbox, like approvals, the question is around rejections. The plan is to not require comments u2013 but there will be an option to approve/reject. After selecting reject (for example) the user will be able to reject or add comments (or cancel). The question is: Is it OK to not force comments on reject, but to make it optional only?

So u2013 please let us know what you think!

Thanks!

Ginger

[Former Member]

Hi Ginger,

I only worked with some notifications sent as sms to mobiles in the past.

Item 1.

Mobile approval has added value if it allows approvers to immediately get notified of items for approval, actively asking for a complete list of workitems won't be normal behaviour,so I think I would go for speed instead of completeness .

Item 2.

Make it completely optional. Sometimes you want a reason for rejection and other times the business process isn't that important that it can be optional.

Kind regards, Rob Dielemans