FOUR-14039 | ’Sorry API Failed to Load’ Message in Process and Template Listings

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[mcraeteisha]

Issue

Ticket: FOUR-14039

After attempting to delete a Process Category that has a Process assigned to it, a 'Sorry API failed to load' message appears right before Processes, Templates, and Categories load.

Solution

Add error handling in DataLoading.vue for attempts to delete categories that have processes assigned.

How to Test

1. Go to branch observation/FOUR-14039 in processmaker.
2. Go to Designer → Processes.
3. Go to the Categories tab.
4. Attempt to delete a category that is assigned to a Process.
5. After receiving the error message, go to the Templates tab. Page through the Templates.
6. Go to the Processes tab. Page through the Processes (if you have enough Processes).
7. When Processes and Templates are loading, a 'Sorry API failed to load' message should not appear.

ci:next

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
..

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube