1. Implementing Onboarding (Transitions)
  2. Operation Mode

Operation Mode

The operation mode can be changed for service, configuration, or implementation purposes.

Three operation modes are available:

  • implementation

  • maintenance

  • production

System administrators have the ability to switch to maintenance mode or production mode for each product individually or for all. Products supported by the operation mode feature are:

  • Recruiting (includes Remote Manager Experience)

  • Performance

  • Career Section

  • New Hire Portal

  • Onboarding (Transitions)

For the above products, except the New Hire Portal, system administrators know the number of users using both the product as well as the administrative area related to the product. Note that candidates/new hires who are doing their Onboarding (Transitions) processes are logged into the Career Sections, not into the New Hire Portal.

Implementation Mode: The implementation mode is usually only for new customers or new zones (databases). It is used during the initial configuration and implementation stages of the system. Once the implementation is completed, the implementation mode is no longer available to system administrators and a request must be made through Oracle Support. In implementation mode, system administrators can:

  • Create, delete and modify the Organization-Location-Job Field structure.

  • Create, delete and modify levels in the Organization-Location-Job Field structure.

  • Create, delete and modify elements in the Organization-Location-Job Field structure.

If Recruiting is in implementation mode, users cannot connect to the Remote Manager Experience.

f changes need to be made to the structure of the database after implementation, system administrators must contact Oracle Support and request that the system be put back into implementation mode.

Maintenance Mode: The maintenance mode is a special administrative feature used to protect the integrity of the database when editing Organizations, Locations, or Job Fields.

In maintenance mode, the application is inactive. All users, except system administrators, are logged out automatically. The application displays a message to users as well as to candidates in Career Sections, indicating that the application is in maintenance mode. If users are logged in and have not saved data they were entering, this data will be lost.

In maintenance mode, system administrators can:

  • Delete departments, both via Integration and SmartOrg.

  • Delete positions, both via Integration and SmartOrg.

  • Import job positions via Integration.

  • Modify the Organization-Location-Job Field structure, both via Integration and SmartOrg.

  • Modify levels in the Organization-Location-Job Field structure, both via Integration and SmartOrg.

  • Edit Organization, Location, and Job Field elements (Element Management), both via Integration and SmartOrg.

There are no transactions in Onboarding (Transitions) or Performance that require the maintenance mode. If Onboarding (Transitions) is in maintenance mode and a user is performing a Start Onboarding (Transitions) Process or a Cancel Onboarding (Transitions) Process action from Recruiting, the transaction will still be scheduled to process.

If Recruiting is in maintenance mode, users can connect to the Remote Manager Experience.

Production Mode: In production mode, all users as well as guests, agents, and system administrators have access to the application. In production mode, system administrators can:

  • View structure elements for Organizations, Locations, and Job Fields.

  • Save agencies, both via Integration and SmartOrg.

  • Create and edit job templates.

  • Select and view positions.

  • Create and edit departments.

All tasks listed above can also be performed in maintenance mode and in implementation mode.

To import/export candidates (by Integration) and move candidates in the candidate selection workflow (by Integration), the system must be in production mode.