I have a question about working with CustomForms. I would like to implement a function/search in SuiteScript that would search for CustomForm by Name instead of ID. Any suggestions?
Not sure I 100% get the problem, but see if this doen't help:
Remove code from email to support case script that sets field "customForm".
Create specific role for user used to create the cases - don't assign a generic role, like "administrator".
In code for script, specify the role you created in #2 for the login/authentication.
Now, you can flip back and forth between forms from the NetSuite UI by making the needed form the default for the role you created in #2.
All other users will be unaffected, and you won't have to modify the script going forward, except if you have new functionality to add to it.
The other option is to always make the script use the standard case form. That way, you'll never really need to change it. The standard form will contain all custom fields and all standard fields. The only thing you would then need to control is the preferred form by role.
You need to do the development in sandbox environment and test it there completely before doing the production deployment. You can ask your support team to stop for few minutes while doing the deployment and then do a quick smoke test if possible.
Related
I've read in some articles that it's best practice NOT to add DB users via flyway db migration. It's not very clear to me as to why it's not a good practice. One thing we thought about is that it might be good to have the user configuration automatically documented in the code.
One article mentioned that you might want different user configuration for different environments. But you could also control that in flyway.
When/why would you not want to add DB users using flyway DB migration?
If I'm deploying a new user for the database that will be common across all environments, I would absolutely make the creation of that user a part of the Flyway deployment scripts. It fundamentally makes sense. "Version 43.43 is where we added the login snarglegrass to the app."
On the other hand, if you are working on setting up different environments with varying permissions, I probably will make that part of the flow control commands in pre/post deployment scripts instead of using Flyway. The reason for this is because it can be challenging to write the scripts in such a way as they're repeatable and safe. You could still do it that way though.
I'm using a free Microsoft Account (#outlook.com) on VSTS. I created my first proyect, configure it and make it works with CI/CD. Now, I'm creating a new proyect and I want to add a build definition, but I don't know why, all the options appears disabled.
No matter what I do, the Save button remains disabled.
¿There is a limited number of projects to use with CI/CD per account?
Thank's in advance
This is a very strange behavior, but finally I found the solution: in the querystring params you need to remove the "path" parameter (path=%5C)
Reference: https://developercommunity.visualstudio.com/content/problem/203956/build-definition-buttons-are-greyed-out.html
I'm not the first person to run python scripts that require plain text credentials for third party web services as scheduled tasks.
Answers to these questions provide some ways to obscure or otherwise keep sensitive information out of sight. I like the ssh-agent solution because it avoids the need for a file somewhere containing this information but I don't think I can implement it in my environment.
I'm curious as to why the general approach is not to require the user to input the information as command line arguments like
python myPythonScript.py UserName Password
If these parameters are defined in the scheduled task, I think only the logged in user would be able to access the task definitions. This probably isnt any worse than obfuscation.
I have to use Windows; surely scheduled task definitions are not accessible by all users... (I checked using the answer to How to find the location of the Scheduled Tasks folder and you need admin rights to access that folder)
Before I go ahead and use this approach, is there a reason why this would be a bad idea?
I would encrypt my password(s) rather than doing something like that. Another potential problem is your bash history will now have your password in it.
Does anyone know of any way to export user and role permissions, and then re-import them on another copy of Sitecore?
I've had a search around, and bar writing a bit of code to do this, doesn't appear to be anything immediately available ...
The permissions are actually stored on the items themselves, not the Role or User objects. There are two ways to export the object like Stephen mentioned, perform the export/import on the item you granted/revoked access to, not the role or user.
There are two ways to do this .. you can make a Sitecore package and add them to that, the other way is to use Serialization which will write text files to disk that you can then restore into another sitecore instance.
The choice very much depends on how many users / roles you have to move. If its just a few, you can use a Sitecore package but if you have a lot you will probably want to use serialization to do it.
More info about each topic can be found here..
Serialization Guide
Info on Packages
I'm not sure if this is the correct StackExchange site for this, so I apologize if it's not.
Is it possible to create subprojects in Redmine and have it automatically inherit the member permissions from the parent project? If I've got User A as Manager and User B as Developer on the parent, I'd like it to automagically set that up on the new subproject.
I've searched high and low and can't find a way - internal or plugin - to do this.
Thanks!
That's actually very simple: All you have to do is to go into the administration panel, display the list of projects, find the parent project and use the copy button to create the sub-project. On the next page you can configure your project, pre-filled with the values of your parent project, and have some more options like copying members.
Of course this works only on creation - once you created the sub-project and you change one project, you'll need to change the other one as well. Fortunately, working with groups makes it very easy (configure access for groups, not users).
This is possible now since Redmine 2.3.0 (see issue #5605 for discussion). When creating (or updating) a project, you can simply check the Inherit members checkbox.
(This option wasn't available in Redmine when this question was asked and answered initially, so I'd be happy if you considered changing the accepted answer to this one, thanks!)
That's not possible. One of the most fundamental facts of the Redmine permission system is that users are members of distinguished projects having one or more roles. The permissions can't be inherited. In fact, the possibility to have an issue tree was added rather late and hasn't yet been reflected in the permission system.
That said, even if it could be done, permissions could only be added, as you can't take away permissions using roles (permissions from multiple roles are always added). So you would end up with only the possibility to add more permissions in subprojects, but not with less.