Implement eTag to the Modal for Cases

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892

[estebangallego]

Issue & Reproduction Steps

To improve performance and user experience, we need to preload all cases into the cache when the + Case button is clicked. This reduces load times and ensures a smoother interaction.

In this scenario, we utilize the ETag implementation to enhance the caching mechanism for the start_processes endpoint.

Solution

• Implemented the ETag middleware for the start_processes endpoint to enable efficient response caching and validation.

How to Test

1. Ensure the application has a substantial number of cases to work with.
2. Click the + Case button to initiate the modal.
3. Verify that a 304 Not Modified response is returned for cached data, confirming the ETag implementation is functioning correctly.

• ci:deploy

Related Tickets & Packages

• Ticket: FOUR-20920
• eTag: FOUR-20929

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[tokensPM]

QA server K8S was successfully deployed https://ci-2c97f2b7dd.engk8s.processmaker.net

[eiresendez]

Closing in favor of:

#7892