Skip to content
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

FOUR-17008: [next] Define a value when the config is Email Server 1, 2 #7035

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

pmPaulis
Copy link
Contributor

@pmPaulis pmPaulis commented Jul 4, 2024

Issue & Reproduction Steps

Define a value when the config is Email Server 1, 2...

Related Tickets & Packages

  • FOUR-17008

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

@pmPaulis pmPaulis changed the title FOUR-17008 FOUR-17008: Define a value when the config is Email Server 1, 2 Jul 23, 2024
@pmPaulis pmPaulis changed the title FOUR-17008: Define a value when the config is Email Server 1, 2 FOUR-17008: [next] Define a value when the config is Email Server 1, 2 Jul 23, 2024
Copy link

@ryancooley ryancooley merged commit 4b6728d into next Jul 24, 2024
17 of 22 checks passed
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.

3 participants