Skip to content

FOUR-14497: BambooHR Driver Authorization Error #6417

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

Merged
merged 1 commit into from
Mar 15, 2024

Conversation

eiresendez
Copy link
Contributor

@eiresendez eiresendez commented Mar 15, 2024

Issue & Reproduction Steps

There is a validation error when trying to authorize the BambooHR driver.

  1. Go to admin - settings.
  2. Add the Bamboo driver.
  3. Click on the edit and authorize buttons.

Solution

  • This error occurs in drivers using the CData API driver.
  • Since the API driver operates in the background, only the driver's name or API profile should be sent from the UI. In this case, api should not be sent, but rather BambooHR. Therefore, the change from driver to name was made.

How to Test

  • Follow the steps described above; you should not encounter any problems when authorizing the BambooHR driver.
    It can be tested on the CI Server.

Related Tickets & Packages

ci:deploy

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.

Copy link

@tokensPM
Copy link

QA server K8S was successfully deployed https://ci-74167948d3.engk8s.processmaker.net

@ryancooley ryancooley merged commit d3c2d65 into develop Mar 15, 2024
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.

4 participants