Mobile Friendly Process Apps Recommendations

This post could be useful for process app developers who want to create apps compatible with SBM Mobile Client. Here we gathered few recommendations on how to make process app “mobile friendly” and avoid some known limitations.
 

1      Check “Enable options for SBM mobile app” in composer

If this option is disabled, users will not see the application in SBM mobile. Submit forms will not be available, in will not be possible to select this application in work center. However, application will still be available in Service Catalog unless administrator hides it intentionally.

Checking it enables most of the possibilities mentioned below.

 Find the option under Workflow Design -> [Application] -> Options.

 

2      Use simple mode

Simple mode is mobile client feature, which allows simplifying big forms by and hiding all unnecessary controls. User can quickly switch to full view if it is needed, but the idea is to show minimum sufficient amount of controls on mobile form.

See an example simple and full view on the screen shots below.

 

By default, only required fields will be shown in simple mode. To choose which controls will be available in simple mode go to Visual Design, select some control, Property Editor -> Mobile -> Mobile client forms. Possible options are:

“Always show” – the control will be shown both in simple and full view.

“Always hide” – the control will be hidden on mobile.

“Hide in simple view” – the control will be shown only in full mode.

Besides controls, list of transition on a state form can be shown differently in simple and full view. Keep only most important transitions in simple mode. To adjust it go to Workflow Design -> select transition -> Property Editor -> Options -> Transition button on mobile form.

3      Hide transitions and controls which doesn't work on mobile

If some transition relays on unsupported features – hide it on mobile by setting “Transition button on mobile form:” option to “Always hide”. Same approach can be applied to unsupported form controls, for example widgets.

4      Avoid using JavaScript

JavaScript is not supported on mobile, when possible use build-in form actions instead. If your form heavily relies on javascript logic you may want to hide this transition as was described above.

4.1     Use rules

Since SBM 11.3 “a rule evaluates to true or false” condition is supported. You can use it instead of some java script, for example to compare values of two fields.

4.2     Use values substitution

Sometimes values need to be collected from few controls and set to another. To achieve this without java script use set field value action or refresh with string substitution.

Note: refresh is available on mobile since SBM 11.3

5      Use isMobile condition

In form actions new condition is available “the current form is (not) a mobile form”. It can be used to perform some actions only on mobile or only in web forms.

For example, you can disable some custom (java script) actions or provide alternative logic for mobile. Or in case if you want to block mobile user form this form add something like “on form loaded, if is mobile then cancel this form”.

6      Avoid using html to style the form

Styling form with html tags will not work on mobile. Use set foreground / background color form actions instead.

7      Email templates

Use $MOBILELINK() tag in email notifications templates alongside with $LINK() to provide links to items which will be opened in mobile app.

For example, email template could look like this:
Please click the link below to view the details of this service request:
$LINK( TRUE )

To launch mobile app, please click the following link:
$MOBILELINK( TRUE )

And the result will look like this be:
Please click the link below to view the details of this service request:

http://servicedesk.serena.com/tmtrack/tmtrack.dll?View&I=18096&T=1168

To launch mobile app, please click the following link:

srcmobile://servicedesk.serena.com/tmtrack/tmtrack.dll?View&I=18096&T=1168

  

8      Avoid using decision nodes with two transition forms in a row

In some cases workflow can be designed in such way that going through decision node causes two or more transition forms to be shown to user, currently such scenario is not supported on mobile. User will only see first transition form and all the rest will be skipped if no error occurs.

On a screenshot below such case is represented by Transition -> Decision -> Branch path. If “Branch” transition has some overridden required fields or is unsupported, then the transition will be automatically canceled on mobile.

9      Be aware of unsupported transition types

Currently not all transition types are supported on mobile. If the transition is Post, Subtask, Publish, Copy or External Post it will not be available on mobile.

 

10  Avoid inserting important controls into “Form features” containers

Currently form header, footer and Sidebars are not supported on mobile. So any controls put there will be absent on mobile.

 

I hope this recommendations will help you to build better apps!
And if you have any questions, feel free to ask them in the comments below.
SBM Mobile clients are available in App Store and Google Play.

How to save and reuse a partially filled submit fo...
New in DA 6.1.5: Published Views tutorial

Comments 1

 
Martina Je on Wednesday, 19 September 2018 01:34

Recently I update iTunes browse the top music to downloads in iTunes. But when I use it so I am redirecting my iTunes and get an iTunes error 1671 . I don't know why it will occur. Because it is update issue but I didn't get any update a while ago. Tell me what should I do to understand them.? I just found this link to sort my iTunes error with this https://www.mactechnicalsupportnumbers.com/blog/itunes-error-1671/ I hope it will help for me.

Recently I update iTunes browse the top music to downloads in iTunes. But when I use it so I am redirecting my iTunes and get an iTunes error 1671 . I don't know why it will occur. Because it is update issue but I didn't get any update a while ago. Tell me what should I do to understand them.? I just found this link to sort my iTunes error with this https://www.mactechnicalsupportnumbers.com/blog/itunes-error-1671/ I hope it will help for me.

Recent Tweets