-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
PRIORITY-highSIA-not requiredTasks where Security Impact Analysis (SIA) is not needed.Tasks where Security Impact Analysis (SIA) is not needed.enhancementNew feature or requestNew feature or request
Description
Name and Version
0.4.0
What is the problem this feature will solve?
The backend should automatically generate createdAt and updatedAt timestamps for entities based on the transaction time. This ensures consistency in timestamp management across the system. Additionally, during the import process, the createdAt timestamp can be inherited from the imported data if specified.
What is the feature you are proposing to solve the problem?
Acceptance Criteria
- The backend automatically generates createdAt and updatedAt timestamps for all entities based on the transaction time.
- For new entities:
** createdAt and updatedAt are both set to the transaction time. - For updated entities:
** updatedAt is updated to the transaction time.
** createdAt remains unchanged. - During the import process:
** The createdAt timestamp is inherited from the imported data if provided.
** If not provided, createdAt defaults to the transaction time. - API responses include createdAt and updatedAt for all relevant entities.
- Clients cannot override createdAt and updatedAt during standard API operations.
- Unit and integration tests are implemented to validate timestamp generation and import behavior.
What alternatives have you considered?
No response
Metadata
Metadata
Assignees
Labels
PRIORITY-highSIA-not requiredTasks where Security Impact Analysis (SIA) is not needed.Tasks where Security Impact Analysis (SIA) is not needed.enhancementNew feature or requestNew feature or request
Type
Projects
Status
To-Do