General
Last updated
Last updated
General includes settings of the subscription timeout, single sender identity, insights, comments, and native.
Under this section, you can set the time for running the job and the threshold time to move the job to archive status.
You can set the time out in minutes to run the scheduled job. If a job exceeds the specified time limit, the job will fail with a timeout error.
Depending upon the timeout cycle, the job runs for an additional 15 minutes
Here you can specify the value after which the completed or paused schedules will be moved to the archived state.
You cannot edit, reuse or perform any operations on the jobs in the archived state.
If this option is enabled, then the emails will be sent using the pre-configured FROM email address like 'no-reply@inforiver.com'.
This setting also applies to share reports, comment notifications, and subscription emails
It's a backend feature. While logging, the data flow tracking in lineage will be enabled by default.
This option is enabled by default so that groups are added to the organization's users list. A user can mention a group or the distribution list in comments, comment digest, or email destination.
Enabling this option will allow editing the native values in the visual.
Inforiver generates an access token when you login. Users would need to login again once the token expires. The token expiry time limit can be configured - the access tokens will be refreshed automatically in the backend, provided it is within the configured refresh token expiry limit.
In this section, we have covered the general settings. Navigate to the next chapter to learn more about the writeback settings.
