cancel
Showing results for 
Search instead for 
Did you mean: 

screen personas - workflow substitution mobile app

0 Kudos

Hi,

We wish to create a mobile app through screen personas/slipstream to enable users to substitute their workflow approvals to another approver. Solution required is one screen with the user name (first and last) of the new approver and the date range. Note - there is no direct transaction code to access the standard screen.

We have tried 2 options -

1) Screen flow (NWBC / Business Client 6.5): My settings > Manage my workflow substitutions. This is a webdynpro application. Std screen flow has two tables on initial screen. Click button 'create rule' and populate the tab with user and dates.

Ideally flavour would skip the initial screen and directly launch the subsequent tab to enter last and first name and validity dates. Tried to create a script to click ‘create rule’ to be assigned to onload event. However, the ‘record’ script option is not available. Is this supported? I have looked at sap note 2181980 and don’t see anything obvious.

We have installed -

Component Version Patch

PERSONAS 300 0006

SAP_UI 750 0009

Service UI5 is activated

2) Alternatively tried using older screen flow: SBWP > Settings > workflow settings > edit substitution. This brings up the initial screen with my name as the originator. Must click on my name, press F5 create substitution. Then enter user to be substituted first and last name. Select user from selection box. Enter validity date from and to, click substitution active flag.

Flavour: I created new text fields on first screen 'first name', 'last name', 'valid from', 'valid to'. Created script to populate values using variables from text fields into std fields in subsequent screens and to skip the subsequent screens.

This did not work. Before pressing F5, I must click on my name. However, my name is not in a field so when recording the script to position the cursor, it does not record set focus action.

Appreciate any assistance you can provide.

Kind regards,

Robyn

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi,

We have resolved this. Rather than trying to record the script we used the object selector and copied the 'press' button code across.

Kind regards,

Robyn