العربية

Start free trialBook a demo

Browse the documentation

Documentation

All appsHow the apps connectTeam workflowsCompare

Apps

HR ManagementRecruitment (ATS)Payroll & WPSTime & AttendanceAccounting & E-InvoicingCRM & Sales PipelineSales Orders & FulfilmentInventory, Purchasing & WarehousingProcurement & TendersConstruction & ContractingContracts & E-SignatureProducts & Online StorePoint of SaleRentalsSubscriptions & LicensingHelpdesk & TicketingSocial Media SuiteInfluencer Marketing & Campaign ROIProject ManagementActivities WorkspaceDocument ManagementPDF Tools & E-SignatureCorrespondence RegisterTeam Chat & CallsMeetings & VideoLearning & Certification (LMS)Asset ManagementFleet ManagementRecognition & GamificationContacts & PartnersNotification CentreReports & DashboardsInsights — Business Intelligence & AppsAI CopilotAI Agents & AutomationAI Diagram StudioWebsite BuilderISO Compliance Suite (Imtithal)App MarketplaceCustomer & Partner PortalSecurity, Access & Compliance

An automation raises a job and someone picks it up

Who is involved

RoleWhat they do
Tenant adminBuilds the rule and checks its run log.
Asset managerWorks the work orders the rule raises.

Step by step

  1. Tenant admin

    Creates a rule: when an asset's condition drops below 50 percent, raise a work order titled Inspect {asset} with high priority due in 3 days.

    What they see:The rule appears with Has not run yet.

  2. Asset manager

    Edits an asset and sets its condition to 40.

    What they see:The asset's page shows the new condition.

  3. Tenant admin

    Opens the rule's run log.

    What they see:A line saying which asset, that a work order was raised, and its priority and due date.

  4. Asset manager

    Opens the maintenance board.

    What they see:A new Inspect card in Open with the asset's name; repeating the same change does not add a duplicate card.

Who is told what

The rule's run log is the record. No bell notification is sent for the raised job.

Related