Time-travel in DXT_Variables

"As-at-date" time-travel via affiliations collection

This tutorial focuses on the impact of the "As-at-date" functionality on the affiliations root collection.

Key Steps

Step 1: Access the Athenian Console 0:00

• Open the Athenian console developer tool.
• Navigate to the supporting documents model.

Step 2: Assemble DXT Variables List 0:20

• If the DXT variables list is not assembled, follow these steps:
  • Click on the merge button to access DXT variables pulled from the current entity data.

Step 3: Review Sample Data 1:20

• Inspect the affiliations root collection to view the current data of directors.
• Note the active and inactive statuses of each director.

Step 4: Reassemble DXT Variables Without As-at-date 3:12

• Leave the As-at-date blank and click the merge button to generate DXT variables.
• Review the affiliations root collection to see the number of records.

Step 5: Set an As-at-date 3:20

• Choose a specific As-at-date (e.g., June 20, 2025).
• Click the merge button again to generate DXT variables reflecting this As-at-date.

Step 6: Analyze Updated Affiliations Collection 4:20

• Review the affiliations root collection again to see how the records have changed based on the As-at-date.
• Note any directors that were excluded or had status changes.

Step 7: Document Findings 5:31

• Record how the As-at-date affects the affiliations root collection.

Tips for Efficiency

• Refer to other training tutorials for different time-travel DXT variables used in resolutions, signature block and government forms generated through specific task workflows.

Link to Loom

https://loom.com/share/f0782e474264412d8e887b4b75f9f8f6

Task "Resolution Date" time-travel via RES_collections

This tutorial outlines the steps to populate the res_affiliations collection using task workflows in Athenian, ensuring accurate time-based data representation.

Key Steps

Step 1: Understand Key Date Fields 0:19

• Familiarize yourself with the key date fields in Athenian tasks:
  • Resolution Date (most important for time travel)
  • Effective Date
  • Reference Date

Step 2: Set the Resolution Date 1:25

• In your general task, set the Resolution Date to the desired date (e.g., June 20th, 2025).
• Leave Effective Date and Reference Date blank unless needed for other contexts.

Step 3: Click Generate Documents 1:48

• Navigate to the Supporting Documents section.
• Click on 'Generate Documents' to compile the DXD variables in the developer console.

Step 4: Identify Collection Types 2:02

• Understand the two types of collections:
  • Standard Collections (affiliations, entities, participants): Reflect current state without prefix.
  • RES_affiliations collection: Show a snapshot of the entity affiliations data as of the set Resolution Date.

Step 5: Ensure Resolution Date is Set 2:24

• Always enter a Resolution Date in tasks to ensure RES_collections are generated.

Step 6: Analyze RES_affiliations Collection Data 3:01

• Inspect the RES_affiliations collection to see only active and confirmed data as of the Resolution Date.
• Example: Only directors confirmed as of June 20th, 2025, will appear.

Step 7: Verify Data Structure 4:11

• Check that the structure of variables in RES_affiliations matches that of the standard affiliations collection.

Step 8: Use RES_affiliations for Time-Sensitive Documents 5:01

• Utilize RES_affiliations collections for generating time-sensitive legal or compliance documents.

Step 9: Experiment with Test Data 5:35

• Test with different entity data, adding various principals, agents, or share transactions.
• Ensure effective and end dates are recorded as needed.

Step 10: Create Dummy Task 5:46

• Create a dummy task in Athenian with different Resolution Dates to observe changes in different RES_collections.

Step 11: Assemble DXT Variables 6:00

• Assemble DXT variables in the console to see how RES_affiliations respond to time changes.

Cautionary Notes

• Always set a Resolution Date to ensure populate time-travel RES_collections.
• Be aware that without a Resolution Date, RES_collections will not be created.

Tips for Efficiency

• Use RES_collection to code compliance and other resolutions documents
• Regularly practice with test data to become familiar with the process.
• Document any common issues or questions that arise during the process for future reference.

Link to Loom

https://loom.com/share/c3a122f1062d480c9c0d6abd1adc7aa8