Skip to content

ERS-32863: Preparing documentation for soon to be externalized report events #1410

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

RoseWyatt
Copy link
Contributor

@RoseWyatt RoseWyatt commented Apr 14, 2025

This PR's primary goal is to add documentation for the soon to be externalized Report Updated and Report Deleted events.

Additional tweaks:

  • Tables reformatted to be readable and have a consistent structure.
  • subtopic is not exposed to customers and so is being removed from all expense event documentation.

@RoseWyatt RoseWyatt marked this pull request as draft April 14, 2025 02:19
@RoseWyatt RoseWyatt changed the title Update v4.expense-events.md ERS-32863: Preparing documentation for soon to be externalized report events Apr 14, 2025
| `lastModifiedDate` | `timeStamp` | RFC 3339 | **Required** Current system time (UTC) when the event notification is issued. |
| `href` | `string` | RFC 3986 | URI of the report resource that can be called via the Expense v4 API. |

### Report Updated Event Schema
Copy link
Contributor Author

@RoseWyatt RoseWyatt Apr 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Start of newly added event tables.

| `reportId` | `String` | `Alphanumeric` | **Required** Unique identifier of the newly created expense report. Maximum characters: 20 |
| `reportType` | `String` | `Enum` | **Required** This value identifies the method used to create the report. Supported values: <br>Regular, <br>Reconciliation, <br>Statement, <br>AutoCreated |
| `lastModifiedDate` | `timeStamp` | RFC 3339 | **Required** Current system time (UTC) when the event notification is issued. |

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

End of newly added event tables.

| `route` | `String` | `String` | For internal use. This will be set to stable. |
| `topic` | `String` | `Enum` | **Required** Identifies the topic that the event belongs to `public.concur.expense.report`. |
| `eventType` | `String` | `String` | **Required** Event Type: `reportCreated` - Identifies the event type on the topic. |
| `subtopic` | `UUID` | RFC 4122 | **Required** Unique identifier of the company the report belongs to. |
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Corrected, this is populated by company ID for report created events.

Only status changed events populate subtopic with report ID.

@RoseWyatt
Copy link
Contributor Author

Keeping this as a draft until reviewed by my project manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant