Deeper Understanding

In-App notifications event details

Modified on Wed, 23 Sep at 3:58 PM

TABLE OF CONTENTS


Introduction

This article is quite technical, but gives a complete picture of what types of In-App notifications ShedEx supports, as well as when they are triggered, and to whom they are sent.
The orange headers in table, as well as the Table Of Contents show the types: 


 

Event NameWhen to send NotificationWhom to send Notification toConfig LevelRedirection Link

EA Related 

EA Createdif the partner tenant is differentPartner side Representatives and Owner side representatives (other than the creator)GlobalEA Details Page
EA CreatedFor same tenantPartner side Representatives and Owner side representatives (other than the creator)GlobalEA Details Page
EA SignedPartner signs first (Owner not signed) (Owner Partner Different)Partner side Representatives and Owner side representatives (other than the creator)RecordEA Details Page
EA PublishedOwner signs last (becomes active),
 User with both roles signs, When EA is first published (Owner signs first time, IsRepublished = false)
EA representativesRecordEA Details Page
EA PausedWhen EA.IsActive set to true via ResumeAsync() or status changeEA representativesRecordEA Details Page
EA Resumed
EA representativesRecordEA Details Page
EA ArchivedWhen EA is archivedEA representativesRecordEA Details Page
EA Representative AddedWhen user added to EA.ResponsiblePersons via AddResponsiblePersonAsync()The person addedGlobalEA Details Page
EA Representative RemovedWhen a user is removed from EAThe person removedGlobalWill not redirect

Template Related

Template sharedWhen a template is shared with other tenantsOther setup admins of receiver template sideGlobalTemplate details page
Config Update required due to template updateTemplate is currently being used in configs, so the configs which is using this template will need an updateSetup AdminGlobalConfig Details Page

Config Related

Config UpdatedTemplate updates accepted by owner but partner hasn’t accepted yet (the template is shared between two tenants , and they both have created configs using this template so both of them will need to accept the updates before proceeding to trigger update in EA)Setup admin others identified based on EA usage of different configsRecordEA Details Page
EA update Required Due to Config UpdateTemplate updates accepted by both owner and partner (different tenants), both template has been updated. and corresponding has been accepted in the configs.Owner RepresentativesRecordEA Details Page

Data Transfer Related 

Transfer Event Generated
EA representativesGlobalEA Details Page
Upload Succeeded
Representative, receiverRecordEA Details Page
Download Succeded
Sender side user (uploader)RecordEA Details Page
Upload Failed
EA representativesRecordEA Details Page
Download Failed
EA representativesRecord EA Special: User can configure execution type desktop or autonomous or both (how to do this?)EA Details Page
Upload Failed with Conflict
EA representativesRecordEA Details Page
Download Failed with Conflict
EA representativesRecordEA Details Page
Upload Skipped
EA representativesRecordEA Details Page
Download Skipped
EA representativesRecordEA Details Page

Tenant Related

New tenant request
System AdminSystemSystem Admin Tenant Page
New tenant registerWhen System admin approves or rejects a Tenant Joining RequestSystem AdminSystemSystem Admin Tenant Page
New User register
Tenant AdminSystemTenant Admin Users Page

ILAP Term Related

Connector Failed When a connector test failesTenant Admin/Setup AdminGlobal for Tenant Admin Rolesconnector details page
Global SchedEx Term AddedWhen A Global SchedEx Term is create via the System AdminAll setup Admin of the Userglobal
Product Release Related
New Version Released for {{ProductName}}When a new version is deployed and is set active:
Desktop client: version number
AC: version number
Schedule Analytics: Api version number
All Tenant AdminsTenant admin users can disable for themselves (some can disable)Desktop/AC/SA Installation Center

Time Based

EA ExpiredWhen EA.ExpirationDate < CurrentDate (checked by background job)EA representativesRecordEA Details Page
Upload overdue (Other than on Demand as they become overdue soon)For Exchange agreement which are not On DemandEA representativesRecordEA Details Page
Download OverdueFor Exchange Agreements which are not On DemandEA representativesRecordEA Details Page
EA Expiring SoonWhen EA.ExpirationDate is within 3,7,14 days remindersEA representativesRecordEA Details Page
Service token for Autonomous Component or Schedule Analytics about to expireTrigger: 14 days, 7 days, 3 days remindersTenant AdminGlobal for Tenant AdminProper Service Token Generation Page


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article