FOUR-18601 populate cases_started table - sub processes

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments

[devmiguelangel]

Issue & Reproduction Steps

Populate cases_started table - Sub processes

• The User starts a process that has been assigned.
• The cases_started table is populated with the cases started by the User.
• The process starts a new subprocess request (this does not create a new case, it updates the existing one)
• The system updates the related fields: processes_ids, processes_titles, process_requests_ids. These values must be UNIQUE not duplicated.
• The participants of the sub processes are also updated in the case_started row.
• The user completes all the started requests of the case
• The system updates the status field to COMPLETED, and compleated_at for the created row at cases_started

Considerations:

• In the column processes: Consider the first process must be always the main process (parent process)
• In the column requests: Consider the first request must be always the main request (parent process)

Related Tickets & Packages

FOUR-18601

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.

ci:next

[caleeli]

Please review the comments