如何配置RSA Archer订阅通知实现首次发布日起每6个月触发

Alright, let's tackle setting up that 6-month recurring notification in RSA Archer based on a record's first published date. This is a common requirement, and the key is using calculated fields to dynamically track the next trigger date per record. Here's a step-by-step guide to make it work:

First off, make sure your application has a field that captures when the record was first published. RSA Archer includes a default system field called First Published Date (look under System Fields) that’s perfect for this. If you’re using a custom date field instead, just substitute that in the steps below.

We need a field that automatically calculates the next date the notification should fire—6 months after the last interval starting from the first published date. Here’s how to set it up:

• Head to Application Builder > Applications, open your target app, and go to the Fields tab.
• Click Add > Calculated Field, name it something clear like Next 6-Month Notification Date, and set the field type to Date.
• Paste this calculation into the expression box:

  DATEADD([First Published Date], ((DATEDIFF([First Published Date], GETDATE(), "m") // 6) + 1) * 6, "m")
  

  Quick breakdown of what this does:
  • DATEDIFF counts how many months have passed since the record was first published.
  • The integer division (// 6) tells us how many full 6-month cycles have already happened.
  • Adding 1 and multiplying by 6 gives us the total months to add to the first published date to get the next trigger date.
  • DATEADD crunches that into a concrete date (e.g., if first published was 2018-01-01, the first trigger date would be 2018-07-01, then 2019-01-01, etc.).

Now let’s tie this calculated field to a subscription that sends the notification:

• Go to Records > Manage Subscriptions and click Add Subscription.
• Fill in the basics: give it a descriptive name, add a brief description, and select your target application.
• Under Trigger Conditions, set up this rule:

  [Next 6-Month Notification Date] Equals [Current Date]
  This ensures the subscription only fires on the exact date we calculated for each record.

• Customize the Notification Content: use merge fields like [Record Name] or [First Published Date] to make the email relevant to the recipient.
• Add your Recipients (users or groups who need the alert).
• Under Schedule, set the subscription to run Daily—this way Archer checks every day if any records are due for notification. Don’t forget to set the subscription to Active!

Before rolling this out, test with a dummy record:

• Create a test record and set its First Published Date to a known date (e.g., 2018-01-01).
• Check the Next 6-Month Notification Date field to confirm it shows the correct next trigger date (2018-07-01 in this case).
• To test the notification immediately, temporarily adjust the calculated field to use today’s date as the trigger, then run the subscription manually to verify emails are sent out.

That should do it! Each record will now trigger a notification every 6 months starting from its first published date.

内容的提问来源于stack exchange，提问作者Pallavi Singh