openxapps / itsm-pwa Goto Github PK

When trying to revoke access token, the RSSO throws a 401 and prompt for login via alert modal.

When a new user access the app, the following should happen:

• Default settings gets created locally. This will have no ID, thus notify the user to access the settings route to create a profile.
• Once in the settings route and the user clicks save for the first time, pull back the user's profile ID and trigger a module count API immediately. This action should allow the landing route to show module counts if any.
• Check whether the module count API fetches the data by profile ID or user name.
• Once the user navigates back to landing route, make sure the landing route picks up the user's profile ID.

People module implementation steps

• Add new route to list all my people.
• Add new route to view people profile details.

Before RSSO was introduced to this project, we used Remedy Jetty API for authentication and token management. Now that RSSO took the lead on this, we need to strip out the session code.

Currently the module counters wraps the module title. This looks stupid and need to wrap another element. See what is best. Also refactor the module counter API to update on the fly, rather than fetching what Remedy has stored in the user settings form.

The landing component checks for a valid auth token on render. We've implemented a useEffect hook that checks for a valid token. Additionally we need the follow included during token validation:

• If local storage token is still valid, then pull Remedy settings for current user.
• Compare the Remedy settings timestamp with local storage timestamp. (see note below)
• If Remedy settings timestamp is after local settings timestamp, then replace local settings object with Remedy settings data.
• Also rerender the theme if its different.

NOTE To enable timestamp comparison, first enhance the settings object on local storage to keep a timestamp value. This value will be used to compare against Remedy's Last Modified Date value.

Motivation for this enhancement is to sync settings between Remedy and local storage on any device or browser the user use. The effect of not having this enhancement is that users experience odd behavior when using different devices and browsers, accessing this app.

Implement module counters. A custom remedy form was created that calculates the module counters based on which module shows on the landing route. Use form SBSA:PWA:UserSettings to pull back the counters.

Revisit the auth flow again. Steps seen:

• Login on landing route.
• Open approval list and an auth error pops up.

Also revisit the other routes for auth flow streamline.

Once the app moves to its own web server, we'll need the web host separated from the Remedy API host. At the moment they the same host based on web server sharing.

After rebuilding the token flow, the approval routes got broken. Fix it!

Enhance the asset module as follow:

• Add audit details accordion
  • Last login user and date
  • Last audit user and date
  • Last scan date
• Add work info accordion
• Add ability to comment into the work info
• Add ability to audit asset

Allow the asset route to handle different asset types by:

• Add a meta object that defines the asset type, Remedy form to read from and fields to pull back.
• Change the asset details service to be generic by accepting function parameters based on point above.
• Change the asset view route to import the correct asset type component from the shared components.

Change the Remedy workflow on the settings form to accommodate for individual module actions. Use the KVP to store the action options and add a menu to the zActions field. Update any JS that touch the zActions field via the API.

The design document is out of date and not relevant to the project. Remove the document and folder.

Incident module implementation steps

• Add new route to list all my incidents.
• Add new route to view my incident details.

Replace problem management module with service request management module. Steps:

• Change Remedy problem module workflow to request module.
  • Rename fields showProblem to showRequest.
  • Rename fields problems to requests.
  • Update the filter workflow accordingly.
• Change local storage object and settings route to replace problem module with request module.
• Implement new request route.

• (required) Change header name from Standard Bank ITSM to IT Service Management. Keep same font style, just change the header text.
• (required) Change LandingComponent images and layout.
• (optional) Change the version span to a tiny button (anchor) that will open a new tab to this GitHub repo.
• (optional) Add a new user IconButton on the far right (or make the best choice whether to have the button to the left of the gears button). This will be used to access the user's Remedy profile details later, once we've created a new ProfileComponent route.

Create a new settings service function to allow for on demand module counter updates. This will fire Remedy workflow to calculate module counters on user's settings record.

Change module implementation steps

• Add new route to list all my change requests.
• Add new route to view my change request details.