Take action on your jobs in the Action center

<< Click to Display Table of Contents >>

Raynet One > 1.1 > User Guide > Organize your IT landscape 

Take action on your jobs in the Action center

In addition to the Job list, the Action center empowers direct user activity, e.g. handling of failure in inventory or discovery jobs. Simply said, the Action center serves as a "mouthpiece" between platform and user, notifying users of necessary intervention and encouraging them to interact with the system. Let's dive into the topic of platform event handling.

 

The next series of chapters explains the topic by working on your own IT landscape. Please make sure to have the platform configured correctly for the execution of real platform jobs.

 

finger1

Be aware:
Some step-by-step guides rely on knowledge about work-flows covered in former chapters. Please read this documentation carefully to not trip over more compact step descriptions.

 

clip0293

 

Action center notifications are displayed by the bell icon. It's visible on every web interface view. Click on the icon to open the widget titled Actions required. There are currently no active notifications in the image. The user should be aware about any running platform jobs at any given time. Redundant platform operation is nobody's best friend. Prevent inefficiency, by awareness.

Common event types

These are the types of events described in Action center notifications. Each has a different set of possible actions and consequences.

 

Missing credentials (device or service) [prompt]

This notification is enabled by settings the Behavior on missing credentials option to Ask the user for credentials (default).

 

clip0282

 

Action center widget entry for the missing credentials event.

 

clip0283

 

Prompt in the action center for the credentials to use during the inventory run, since the platform runner is required to authenticate to the device. By clicking on the Add new button, the credentials addition wizard is opened. The one time use option can be toggled to reveal two input boxes, for the plain-text username and the password.

 

clip0284

 

Different missing credentials action center widget entry, in case authentication was attempted with wrong credentials. Please provide correct ones.

 

Newly discovered device [prompt]

This notification is enabled by setting the Behavior on newly found devices option to Ask the user if the device should be inventoried.

 

clip0285

Action center widget entry for newly discovered devices. The user is asked whether to perform an inventory run on them.

clip0286

Prompt in the action center to accept or decline the inventory run offer.

Newly found Oracle database [prompt]

This notification is enabled by setting the Behavior on newly found Oracle databases option to Ask the user if the database should be inventoried or discovered.

 

clip0287

Action center widget entry about newly discovered Oracle databases.

clip0288

Action center prompt providing the user with an array of actions possible on the newly discovered Oracle database. You can either perform discovery or inventory. Clicking on Ignore is going to discard the notification.

Newly found network [prompt]

This notification is enabled by setting the Behavior on newly found networks option to Ask the user if the new network should be discovered (default).

 

clip0289

Action center widget entry for newly discovered networks.

clip0290

Action center prompt about the newly discovered network. You are provided with the option to discover the network. Alternatively, the notification can be dropped by clicking on Ignore. Since devices tend to have a lot of local networks, this notification type can surface pretty often.

No runner available [error]

clip0291

Action center widget entry in case a platform job failed runner selection. Since runners are deployed on critical infrastructure points, the right one needs to be chosen for the specific job.

clip0292

Action center error information giving more details about the critical runner selection failure. Audit your platform's runner deployment and configuration to prevent it in the future.