General

On the General page, you can configure whether to send a notification when execution of a job fails, when a HULFT Integrate service or HULFT Transfer service stops or restarts, when an application is installed or uninstalled, or in other cases.

For functions that are subject to additional fees when usage exceeds a specific value, you can set a threshold (%) based on the value specified in your contract and configure the setting to send a notification if the set value is exceeded.

For details about configuring settings to receive notification via email, refer to Email.

For details about operating the browser notifications on the screen, refer to Screen elements.

General

To open the General page, select > Notifications > General in the navigation menu.

Note

To configure notification settings, either one of the following permissions is required:
- NotificationFullAccess
- NotificationSettingsAdminAccess
To view the notification settings, the ListNotificationSettings permission is required.
There are no settings for browser notifications. Therefore, there are no permission settings, either.

= Remarks =

For the names and functions of basic UI elements and other items of HULFT Square, refer to the following topic:

Screen elements

(1) Jobs: The setting value (On or Off) for notification when execution of a job fails is displayed.
(2) Services: The setting value (On or Off) for notification when a HULFT Integrate service or HULFT Transfer service stops or is restarted is displayed.

= Remarks =
When the scalability for the service is set to "2" or higher, a notification is sent if all the services become unavailable.
(3) Billing: The threshold value that is set in the billing information is displayed.
(4) Edit: You can edit the settings for notifications.

Types of notifications and notification destinations

Email notifications

The notification destinations are as configured in > Notifications > Email.

For details about configuring settings to receive notification via email, refer to Email.

Types of notifications		Link (*1)
Type	Event	Link (*1)
Jobs	Execution of file event job fails	Yes
	Execution of REST API job fails	Yes
	Execution of scheduled job fails	Yes
	Execution of HULFT Transfer job fails	Yes
Services	HULFT Integrate service or HULFT Transfer service starts
Services	HULFT Integrate service or HULFT Transfer service stops
Billing	The usage of the storage currently in use exceeds the threshold configured in General
	The total amount of data transferred exceeds the threshold configured in General
	The total usage of the CPUs currently in use exceeds the threshold configured in General
	The total usage of the memory currently in use exceeds the threshold configured in General
	The number of VPC end points created exceeds the threshold configured in General
	The number of REST API job executions exceeds the threshold configured in General
NAM	Execution of native application module (NAM) fails	Yes
	Native application module (NAM) stops	Yes
	Native application module (NAM) starts	Yes

The underlined sections of notifications are links. Click one to move to the corresponding information. If you don't have permission to access the link destination, an error is displayed.

Browser notifications

With browser notifications, the results of events such as status changes of a HULFT Integrate service/HULFT Transfer service, status changes of an application/native application module (NAM), and successful job execution are sent as notifications.

There are multiple types of events for which notifications can be sent. The notification destination depends on the type of event.

Asynchronous events

The user who executed the event is notified when system events are completed, such as startup of the HULFT Integrate service/HULFT Transfer service and execution of the job.

For example, when you execute a file event of a very large volume, you will be notified that execution of the job was successful. This way, you don't need to continually check the status, because you can be informed through the notification.
Collaborations

When another user in the same group performs an action, the users with the same edit permission are notified.

For example, when Administrator A adds User D to the group, a notification that User D has been added to the group is sent to Administrator B and Administrator C. This way, Administrator B and Administrator C are informed that User D has been added.
Passive events

When another user performs an action, information about the action is sent as a notification. Because the user who performed the action is obviously aware it was completed, no notification is sent to them.

For example, when an administrator grants User A permission to access a workspace, a notification that access has been granted is sent to User A. This way, User A is informed that they have been granted access to the workspace. Because the administrator is the user who performed the action, no notification is sent to the administrator.

Types of notifications and notification destinations are as follows:

When there are multiple event types set for a single event, or if a single action applies to multiple events, multiple notifications are sent.

Types of notifications			Link (*1)
Type	Event	Event type	Link (*1)
Application	Application has been installed (Entire organization)	Passive event	Yes
	Application has been uninstalled (Entire organization)	Passive event
	Application has been cloned (Private)	Passive event
	Application is shared (Internal)	Collaboration
	Application is deleted (Internal)	Collaboration
	Application test is executed	Asynchronous event	Yes
	Application is deployed	Collaboration	Yes
	Application is undeployed	Collaboration	Yes
	New application is added to App Square	Passive event
NAM	Native application module (NAM) is ready for use	Passive event	Yes
	Native application module (NAM) stops	Passive event	Yes
	Native application module (NAM) starts	Passive event	Yes
Service	HULFT Integrate service or HULFT Transfer service is created	Collaboration
	HULFT Integrate service or HULFT Transfer service is updated	Collaboration
		Passive event
	HULFT Integrate service or HULFT Transfer service is deleted	Collaboration
	HULFT Integrate service or HULFT Transfer service starts	Asynchronous event
	HULFT Integrate service or HULFT Transfer service starts	Passive event
	HULFT Integrate service or HULFT Transfer service stops	Asynchronous event
	HULFT Integrate service or HULFT Transfer service stops	Passive event
Job	Execution of file event job succeeds	Asynchronous event	Yes
	Execution of REST API job succeeds	Asynchronous event	Yes
	Execution of scheduled job succeeds	Asynchronous event	Yes
	Execution of HULFT Transfer job succeeds	Asynchronous event	Yes
User management	User is added	Collaboration	Yes
	User is deleted	Collaboration
	Group is added	Collaboration	Yes
	Group information is updated	Collaboration	Yes
	Group is deleted	Collaboration
	User is added to group	Collaboration	Yes
	User is added to group	Passive event	Yes
	Policy is applied to group	Collaboration	Yes
	Policy is applied to group	Passive event	Yes
	Policy is added	Collaboration	Yes
	Policy is updated	Collaboration	Yes
	Policy is deleted	Collaboration
	Permission is granted for policy	Collaboration	Yes
	Permission is granted for policy	Passive event	Yes
Workspace	Workspace is added	Collaboration	Yes
	Workspace is updated	Collaboration	Yes
	Workspace is deleted	Collaboration
	Access to workspace is granted	Collaboration
	Access to workspace is granted	Passive event
VPC endpoint	VPC endpoint is created	Collaboration
	VPC endpoint is updated	Collaboration
	VPC endpoint is deleted	Collaboration
Password policy	Password policy is updated	Collaboration	Yes

The underlined sections of notifications are links. Click one to move to the corresponding information. If you don't have permission to access the link destination, an error is displayed.