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

Configuration on org. level #17

Open
stefanes opened this issue Aug 20, 2019 · 8 comments
Open

Configuration on org. level #17

stefanes opened this issue Aug 20, 2019 · 8 comments
Assignees
Labels
enhancement New feature or request

Comments

@stefanes
Copy link

Please consider allowing configuration of the JSON rules that drive how the cascading picklist works on org. level.

We have many projects but only a few processes, setting this config on each project is unfortunately a showstopper.

@ByAgenT ByAgenT assigned ByAgenT and danhellem and unassigned ByAgenT Aug 21, 2019
@danhellem
Copy link
Collaborator

Thanks for the suggestion. Configuration is actually done based on the field names. So as long as the fields names and values are the same across all projects in your org, it should work just fine.

@stefanes
Copy link
Author

stefanes commented Aug 26, 2019

When I tried the extension I found no way to input config on org level. Has this been added? Or can you point me in the right direction?

@danhellem
Copy link
Collaborator

@stefanes you are right in the fact that it is not setup at the org level. But it is an open source extension that you can go in and adjust from the project level to the org level contribution point. We have not seen anyone else ask for us to make this adjustment. I will re-open the suggestion and see if anyone else chimes in to ask for this change.

@danhellem danhellem reopened this Aug 26, 2019
@danhellem danhellem added the enhancement New feature or request label Aug 26, 2019
@mahony
Copy link

mahony commented Sep 3, 2019

We're also using cascading picklists with the same values and config across multiple projects. I agree that it would be convenient to have the option of a single, org-level config vs. creating and maintaining multiple project-level configurations.

@psjeeper
Copy link

psjeeper commented Apr 2, 2020

We are leveraging this extension as @mahony is and definitely would like to be able to set this as part of the process definition, where it really needs to be, so that it can be applied to specific processes instead of to specific projects.

@clickbidur
Copy link

We decided to use another extension for the same reason, configuration to be repeated for each project. Also would love to have support for 3 levels of dependencies (instead of 2).

@prashanthbv12
Copy link

prashanthbv12 commented Dec 24, 2020 via email

@clickbidur
Copy link

Which extrnsion?
On Thu, 24 Dec 2020 at 4:49 PM, clickbidur @.***> wrote: We decided to use another extension for the same reason, configuration to be repeated for each project. Also would love to have support for 3 levels of dependencies (instead of 2). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK2HROVZ744NDY4OX7MOON3SWMPUBANCNFSM4INRCP4A .
-- Thanks, Prashanth Hand Phone-9844730107 [email protected]

Multi-Pickers Field Control

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants