Skip to main content
Skip table of contents

Triggers & Actions

Must read before starting with Triggers & Actions

Triggers & Actions are very powerful. However it is quite easy to break stuff and impact many flow ons your Peripass environment. Be sure to read all documentation carefully before starting to explore.

Examples of previous “bad configurations” that had major consequences:

  • Sending an email to all visitors every 5 minutes (in a tenant with more then 5000 visitors)

    • Consequence: after 1 hour your emails get blacklisted by major spamfilters. It takes 24h to remove you from the blacklist. In this period you won’t be able to send any emails.

  • Sending an SMS message to all visitors every 1 minute (in a tenant with more then 5000 visitors)

    • Consequence: There was a very expensive cost related to sending this much SMS message.

Peripass has a business rules engine called “Triggers and Actions” to fully customize your business flows tailored to your needs.

The overall concept is:

Steps

Examples

Step 1: When an event happens… = trigger

  • When a transport/visitor/contractor registers

  • When a transport is dispatched

  • When a transport/visitor/contractor uses his PIN/Badge to pass the entry barrier

  • When a sensor detects a transport

  • When an asset’s status changes

  • When a yard task is finished

  • Every monday

Step 2: … under certain conditions … = conditions

  • Only for contractors

  • Only for inbound

  • Only when the product group is “chilled goods”

  • Only when the main entrance is used

  • Only when the transport has arrived after his slot

  • Only between 6 AM and 5 PM

  • Only when the first weighing is done

  • Only for assets of category ‘Container’

Step 3: … then do actions. = actions

  • Give a driver access to the entry/exit barrier

  • Send the driver a text message in his own language

  • Inform the carrier by email

  • Call a 3th party webhook
    (e.g. close the order in SAP)

  • Print a ticket

  • Create a yard task

  • Take a picture

An example to further clarify the concept:

  • Trigger: when a visitor status changes to checked in (= registers on self service kiosk)

  • Condition: and this visitor his active profile is Contractor

  • Action: create a QR entry code for this visitor AND print a ticket with this QR code

Inspiration

Here is some automation inspiration from the field.

  1. When a driver registers for a flow without a dedicated dispatcher → Then flash a light or play a sound in the warehouse to inform the team lead

  2. When a driver registers → Then change the status in the TMS and update the missing information

  3. When a contractor is not entering the site within 20 minutes after he registered → Then create a yard task for the guard to go and check whether everything is ok

  4. When a driver is dispatched → Then add the license plate to the ANPR camera on the entry barrier or generate a new unique PIN code that has access to the entry barrier

  5. When a driver is granted access on an entry barrier → Then take pictures of the outside of the trailer for damage referral

  6. When a transport is dispatched to a QA or sample-check zone → Then create a task for an operator or scientist to perform a QA check

  7. When a wheel block is deployed → Then show a visual indication in Peripass' digital yard

  8. When the documents for a transport are ready → Then communicate to the driver with a text message that he can print his documents on the check-out kiosk and leave the site

  9. When a transport has departed → Then inform the customer of this departure by email

  10. When a transport, visitor or contractor is not updated for 3 months → Then anonymize all personal information such as name and phone number


Explore more

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.