Though the form builder in SSO is pretty good, a huge missing component is the ability to incorporate existing data into forms. Obviously it wouldn't make sense to be able to incorporate ALL the data from the backend (otherwise you'd essentially be replicating the entire database). Some of the most important lists I think that could be able to be incorporated into forms are:
- Active Employee Names
- This would allow custom reports to be built that employees can fill out regarding other employees, such as a team based field level hazard assessment.
- Active Cost Codes
- This would allow cost codes to be used in custom reports. For example, many field level hazard assessments require the activity to be specified. Many labour cost codes activity based, so this would be an easy way to select what activities are being performed.
- Active Jobs/Phases/Work Orders
- Any reports relating to a job/phase/or work order (or multiple) could be easily created.
- Inventory Locations & Equipment
- Sage Parts

The main reason for Inventory Locations and Parts would be so that admin users can build reports that field employees can use that include the company database of parts. One of the biggest hurdles in using SSO is that there is no way to request or manage inventory materials of jobs (but for some reason you can with service. I guess the name "service operations" implies that this is focused on the service module). Anyway, lists would provide a good "workaround" for just about any gap that SSO has a given company's workflow.

As an alternative to parts and inventory locations in lists, if you allowed 12-2 Allocations to be executed from SSO, this would be even better. But if the development team is looking for "bang for the buck", the ability to add lists into reports would allow users to build a report that covers any workflow gaps.

by: Ryan B. | over a year ago | Other