The administrator can control the behaviour of the Simplified Loader mobile app by centrally managing its setup. Any changes to the configuration will immediately be reflected in the app.
Simplified Loader mobile app is linked to a Lookup Type in Oracle Fusion. Using Lookup Type, the administrator assigns access to the users authorized to use the mobile app.
1. Get right Lookup Type linked to the mobile app. The Lookup Type is listed under the App Details section in the Settings page.
2. In Oracle Fusion, navigate to Setup and Maintenance and select the “Search”option from the Task menu. Search for “Manage Common Lookups”
3. Search for Lookup Type displayed in the mobile app
4. Add new Lookup Code: Enter username of the user to be authorized in Lookup Code and Meaning fields
4. Save the record.
5. The registered user can now access the mobile application.
Application control preferences
When a user logs in to Oracle Fusion using Simplified Loader app, their login is validated using Lookup Type in Oracle Fusion. At the time of validation, the Simplified Loader mobile app reads the text entered in the Description field of the Lookups setup. The app uses values entered in Description fields to control the app behaviour.
The Description fields can be set up with the following pre-defined preferences that control the behaviour of the mobile app. The administrator can choose to use one or more preferences. When using multiple preferences, enter pipe (|) delimiter between preferences.
The default behaviour of all Simplified Loader apps is to allow data sharing from the Transaction Details page in CSV format. To stop data sharing, use DisableDataShare preference. The default value of DisableDataShare preference is N. Set the value of this preference to Y to remove data share feature from the app.
Usage: DisableDataShare[Y] or DisableDataShare[N]
Screenshot of Transaction Details page containing data share button (default behaviour).
Screenshot of Transaction Details page with disabled data share functionality ( DisableDataShare[Y] ).
The default behaviour of all Simplified Loader apps is to allow users to log in to the app every day. Admin can restrict the days on which the app can be used with the AllowedDays preference.
Usage: AllowedDays[1,2,3,4,5,6,7] where numbers 1 to 7 represent days of a week. 1= Monday and 7=Sunday. Example: AllowedDays[1,2,3,4,5] will allow users to make use of this app only on weekdays.
The following error message is displayed whenever a user attempts to access the app outside the allowed days.
The default behaviour of all Simplified Loader apps is to allow users to log in to the app at any time. Admin can restrict the time at which the app can be used.
Usage: AllowedHours[HH:MM,HH:MM] example: AllowedHours[09:00,17:00] permits users to log in and use the mobile app between 09:00 and 17:00 only.
The following error message is displayed whenever a user attempts to access the app outside allowed hours.
The default behaviour of the app is to log out automatically when the app is not used for 15 minutes. The 15 minutes duration can be changed by setting up AutoLogoutAfterExitingApp preference and providing the number of minutes as a value.
For example, AutoLogoutAfterExitingApp will force the user back to the login page if the app has not been used for 10 mins. Setting AutoLogoutAfterExitingApp [-1] will end the session immediately as soon as the app is closed. In such a case, the user needs to log in again to use the app. NOTE: The time counter starts when the user leaves the app.
The default behaviour of the app is to allow a data query of the entire history, i.e. from the first day of usage. This can be restricted to a defined number of days by using AllowedPastCalendarDays preference. AllowedPastCalendarDays preference accepts the number of days as preference.
For example, AllowedPastCalendarDays will allow users to query data that is 100 days in past. In this example, if the user were to attempt a query for greater than 100 days, then they will receive the following message:
Your organization has chosen to restrict the query data for the past 100 days only. Please contact your support desk if you need to query data beyond 100 days.
The default behaviour of the app is to display 500 records in the Transaction Details page. The 500 record limit per page can be changed by setting TablePaginationRecords preference and providing the number of records as a value.
TablePaginationRecords will display 100 records in the Transaction Details page. The user needs to use back and forward arrow next to the Smart Search field to navigate to the next page.
Override application control preferences at the user level
Preferences can be set up at the Lookup Type level of Lookup Code (User) level. When the same preference is defined at Lookup Type level and Lookup Code level, then the Lookup Code level preference takes precedence.
For example, the following setup will disable data share functionality from all users using the app linked to the given lookup.
The following screenshot demonstrates setup with preference override at the user level.
Your organization may wish to utilize a selection of the available dashboard graphs. If so then the BI administrator can update the SQL in BI Data Model and SQL block related to the graph that needs to be removed form mobile dashboard. Changes made in the Data Model will immediately be reflected in the mobile app and will be apparent to users when they next log in.
Note: A backup should be kept of all changes made to BI Data Model.
Customize data selection criteria
The SQL Data Model can be changed to accommodate any changes in SQL filter criteria. You can only modify filter criteria, but you must not change the SELECT clause. Below are some examples of SQL changes:
1. Restrict user from querying data that is more than a year old. To implement this filter, add the following condition:
AND 365 >= :DAYS
2. Commission specific graph to named users: To implement this filter, add the following condition in SQL Data Model:
AND :SL_USER_NAME IN (‘user 1’, ‘user 2’)
NOTE: Code demonstrated above is only an example. You could make other changes to the WHERE clause of the SQL statement.