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

Search for standard changes within custom template tables #253

Open
OskarMarthinussen opened this issue May 12, 2023 · 1 comment
Open
Labels
needs_research Further research is needed to determine the feasibility and scope of the issue. type/enhancement New feature or request

Comments

@OskarMarthinussen
Copy link

SUMMARY

Enable the ability to search for standard changes within custom tables, instead of being limited to finding templates solely in the 'std_change_producer_version' table.

ISSUE TYPE
  • Feature Idea
COMPONENT NAME

servicenow.itsm.change_request

ADDITIONAL INFORMATION

In my scenario, the standard change I'm searching for is stored in a custom table, which makes it difficult to locate the corresponding template. To address this, I suggest implementing an optional parameter called 'template_table' in the 'find_standard_change()' function. This parameter would allow users to specify a custom table for searching the standard change. To ensure backward compatibility, the parameter could have a default value of 'std_change_producer_version'.

  - name: Create servicenow change
    servicenow.itsm.change_request:
      instance:
        host: "{{ servicenow_change_instance }}"
        username: "{{ servicenow_change_username }}"
        password: "{{ servicenow_change_password }}"
      type: standard
      state: new
      other:
        company: "{{ servicenow_change_company }}"
      template: "{{ servicenow_change_template }}"
      template_table: "{{ servicenow_change_template_table }}"      <-- New parameter with standard value
    register: snow_change_request
@tima tima added type/enhancement New feature or request needs_research Further research is needed to determine the feasibility and scope of the issue. labels May 16, 2023
@Akasurde
Copy link
Member

resolved_by_pr #254

@Akasurde Akasurde removed the needs_research Further research is needed to determine the feasibility and scope of the issue. label Jul 14, 2023
@Akasurde Akasurde added the needs_research Further research is needed to determine the feasibility and scope of the issue. label Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_research Further research is needed to determine the feasibility and scope of the issue. type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants