Previously when using the Stat Windows client, log entries could be created, and text could be added to them while still being able to switch to oher windows/areas of the CSR. So, for instance, one could create a migrator log that stated that a migration...

We are upgrading from Stat 5.7.3 to 5.8 and noticed that when you move to another queue the queue owner field is auto-filled Stat 5.8). Users say that it is easier to have the field blank and would like to have it reverted back.

There will be companies planning to move STAT to the Microsoft/AWS Cloud in the future. However, currently STAT SCA install does not support silent install. It would be a great/added value to the product if STAT can support STAT Central Client silent...

I think it is currently 18 char. It should be 35 char, based on PeopleSoft oprid of char 30, so, STAT_[oprid]

There is no field for adding Business and Functional users in the CSR. Separate Business and Functional user fields are required. This should also have a feature to send updates to the Business User as well as Functional User. In addition to above...

Mass Migration by Release is an attractive looking feature but, in our experience, not really practical. I would be useful to be able to change the migration order of CSRs, Archive Sets, and Objects at the release level (which I'm sure was in 5.6 but...

Limitation with the directory setup. Currently we cannot make it configurable to have the object migrated to the product specific custom top directory. Instead of /oracle/apps/, we would like the object migrated to the specific custom top ex: $JAVA_TOP...

Currently, the business rules report in the criteria section shows the CSR status in Code form. For example, MIGRA is shown for "Migration Approved". Furthermore, when the criteria for the business rule's operator selected is "Changes From" (chg from...

Will STAT have Mobile compatible forms or App or features? this will be very useful feature for non dev/dba to monitor and approve while they are remote.

It would be nice to have a table that stores what hot fixes were applied to the Stat application. Similar to what PeopleSoft does when patches and fixes are applied.