The new web user interface requires that a number of additional new tables be maintained with data in order for users to take advantage of the functionality.

  • By default all users are allocated with the “Default Web User Role” which provides access to the default actions and metrics. This controls which actions and metrics the users sees in the web UI. By default the ones shipped with Transport Express are:

Actions:

  • View all changes awaiting my approval
  • View all changes awaiting my testing
  • View all my in progress changes
  • View all in progress changes for my team

Metrics:

  • Awaiting my approval
  • Awaiting my testing
  • My in progress changes
  • In progress changes for my team
  • In progress changes for project

To maintain other roles to alter the actions and metrics that are available to users please see tables:

  • /BTI/TE_WEBUICFG: General web UI parameters / config table
  • /BTI/TE_USERPREF: Web UI User preferences table
  • /BTI/TE_ROLEACT: Role actions table to link the user roles to the default actions
  • /BTI/TE_ROLEMET: Role metrics table to link the user roles to the default metrics
  • To enable the “In progress changes for my team” each user will need to be allocated to the task groups that represent their team. This will then allocated all tasks for those groups to the team. (See /BTI/TE_USERGRPS table)
  • If user pictures are required these can be uploaded into the Transport Express Domain Controller system. This will then automatically show the user picture in the screen header, news items, recent activity, task list and task details views. See the instructions for the USERPIC_PREFIX field in the /BTI/TE_WEBUICFG table.
  • In addition a new background job is needed to generate data for the web UI News and My Recent Activity feeds. (See Background Jobs)
  • By default the primary tester of the task is designated as the task owner unless a user role is attached to the task to override this. See the details for the TASKOWNER_ROLEID field in the /BTI/TE_WEBUICFG table.
  • The Projects views will show project management information for projects where phase data has been maintained. If nothing is maintained for a project the message “No phase data exists for the selected project” will be displayed. To maintain the data use tables:
  • /BTI/TE_PHASE: Project phases table
  • /BTI/TE_PHASSTAT: Table to assign the task statuses to the project phases
  • /BTI/TE_PRJPHASE: Table to assign the project phases to a project along with the start an end dates

To enable the new web user interface some services need to be activated in SICF:

  • default_host -> BTI -> te_web_services
  • default_host -> sap -> bc -> bsp -> bti -> te_bsp_new

Other general BSP services may also need to be activated to enable the web interface to work.

  • All subnodes in default_host -> sap -> public -> bsp -> sap
    Once activated, you can test the service to determine the URL:
  • http://:80/sap/bc/bsp/bti/te_bsp_new/index.html

You will be prompted for a logon to the Transport Express domain controller SAP system. Use your SAP username and password.

Once logged on, you will be able to access the available functionality and this can be used simultaneously with the Transport Express windows client.

Email notifications: To ensure that approval and testing emails direct the user to the new web UI please ensure that the BSP sever address parameter in the email notification program variant (/BTI/TE_RNOTIFICATION_ENGINE) is set to the correct value. E.g.

  • http://:80/

Tables
All have Table Maintenance dialogs.

/BTI/TE_WEBUICFG General web UI parameters / config table
Field Description
GENERIC_USERPIC Name of generic user picture (/BTI/TE_WEBUI_USER_PIC_GENERIC)
TE_USERPIC Name of Transport Express user picture (/BTI/TE_WEBUI_USER_PIC_TE)
USERPIC_PREFIX Name of user picture prefix
In order to show user pictures in the web UI the images need to be uploaded and stored on the TE domain controller via transaction SMW0.
Choose option “Binary data for WebRFC applications” option.
Each user will require an entry with an uploaded user picture and a naming convention should be used so they all have the same prefix ((e.g. ZTE_WEBUI_USER_PIC_).
It is mandatory that the user ID follows the name prefix otherwise the user pictures cannot be located by TE.
E.g. for user TEUSER it would need to be ZTE_WEBUI_USER_PIC_TEUSER
USERPIC_URLPREFX URL prefix for user picture (/bti/te_web_services?action=GETUSERPICTURE&uname=)
DEFAULT_ROLEID ID of the Role to be used for all users if one is not allocated individually in /BTI/TE_USERPREF
Role ID 00000000000000000000 (Default Web User Role) is delivered as standard
TASKOWNER_ROLEID ID of the Role to be used to default the task owner. Based on the user roles defined in /BTI/TE_ROLEU in the TE config “User Roles” tab.
A “Task Owner” role could be specified and attached to each TE task. This can then be configured in this field for use in the web UI.
If a role is specified here this will be automatically attached to all tasks when they are created and assigned with the user who is creating the task.
The default tester of the task is designated as the task owner if not role is specified here to override this.
NUM_NEWSITEMS Number of news items to display in the “News” feed. The default is 50
NUM_RECENCTACT Number of items to display in the “My recent activity” feed. The default is 50
TL_GROUPBYID Default task list group by option for all users
EXCLUDE_COMPLETE Exclude tasks where the deployment status is “Deployment Complete” from the task metrics
INC_CURUSER_NEWS Include the current user activities in the “News” feed. If not set the logged in user activities will not be shown in the news as they can be viewed in the “My recent activity” feed anyway

The user roles are maintained in TE configuration on the User ROles tab.

/BTI/TE_USERPREF Web UI User preferences table
Field Description
UNAME User name
UIROLEID ID of the default role to be used for the user in the web UI. Based on the user roles defined in /BTI/TE_ROLEU in the TE config “User Roles” tab
If this is not specified, the role in /BTI/TE_WEBUICFG-DEFAULT_ROLEID will be used
DB_FILTERID Last selected filter on the Dashboard Overview screen (auto populated by TE)
DB_PROJECTID Last selected project on the Dashboard Overview screen (auto populated by TE)
PM_FILTERID Last selected filter on the Dashboard Projects screen (auto populated by TE)
PM_PROJECTID Last selected project on the Dashboard Projects screen (auto populated by TE)
TL_GROUPBYID Last selected group by on the Task List screen (auto populated by TE)
/BTI/TE_USERGRPS User groups table to allow users to be assigned to teams based on the task group
Field Description
UNAME User name
TASKGROUPID Task Group ID of the task group that the user is to be assigned to. This will then associate all tasks that have this group to the user’s team
/BTI/TE_ROLEACT Role actions table to link the user roles to the default actions
Field Description
ROLEID ID of the role to be used. Based on the user roles defined in /BTI/TE_ROLEU in the TE config “User Roles” tab
Entries for Role ID 00000000000000000000 (Default Web User Role) are delivered as standard and can be copied to create further roles
ACTIONID The Action Id of the actions to be assigned and displayed for the user role
SEQUENCE The sequence the actions should be displayed in
/BTI/TE_ROLEMET Role metrics table to link the user roles to the default metrics
Field Description
ROLEID ID of the role to be used. Based on the user roles defined in /BTI/TE_ROLEU in the TE config “User Roles” tab
Entries for Role ID 00000000000000000000 (Default Web User Role) are delivered as standard and can be copied to create further roles
METRICID The Metric Id of the metrics to be assigned and displayed for the user role
SEQUENCE The sequence the metrics should be displayed in
/BTI/TE_PHASE Project phases table
Field Description
PHASEID Unique Id for the project phase
PHASE_DESC Description of the phase (e.g. Blueprint, Realisation, Final preparation, etc.)
/BTI/TE_PHASSTAT Table to assign the task statuses to the project phases
Field Description
PHASEID Id for the project phase
STATID Id for the relevant task deployment or planning status
STATTYPE Selection of deployment or planning status
/BTI/TE_PRJPHASE Table to assign the project phases to a project along with the start an end dates
Field Description
PROJID Id for the relevant project
PHASEID Id for the project phase
SEQUENCE The sequence that the project phases should run in
START_DATE The start date for the project phase
END_DATE The end date for the project phase

Background Jobs
In order to generate the data for the web UI News and My Recent Activity feeds a background job is required to run every 5 or 10 minutes to execute program /BTI/TE_RUNEWS_UPDATE.

In the program variant the “No. of days to retrieve events” parameter should specify the number of days that the News / My Recent Activity is required to be reported for. The default is 60 days but in reality this would be much less.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment