I am new to Alfresco.
I want to add a new action in Manage Rules apart from copy, check in, check out, send mail.
I just want to display this action in UI under Manage Rules.
I tried to add in share-config-custom.xml file but the new action in not appearing in new
So which files do I need to change to make the action visible in Manage rules?
One of the tutorials I've written covers this. It is called Creating Custom Actions in Alfresco.
But to save you some reading, if you've written your action and configured it in Spring, Share will pick it up automatically and make it available in the rule configuration. If that's not happening you must have missed a step.
Note that the "UI actions" you see listed in the Share config are different from "rule actions" which is what shows up in the rule dialog.
Related
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
Currently I am writing an app that shall be extended using bundles.
Now the app registered the menu "related" as a service.
Bundle A shall be able to extend the menu and add a link to "imprint".
Bundle B shall be able to extend the menu by adding "disable" and "rename" menu items,
but only when the current doctrine entity is \App\Entity\User.
The target routes will need the ID of the current shown doctrine entity.
Currently I am doing this via events. But as those things above are not events the attempt is wrong.
In addition I don't know how to access or register the current shown doctrine repo / entity.
How to correctly solve this in Symfony?
Is there a neat way to save some performance?
I am thinking of code that will be executed with every request.
Someone in the IRC/Freenode told me, that Symfony has some solutions to avoid such calls for "almost static data".
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.
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.
We have a need to programmatically access the layouts/ templates of one sitecore site and move it to another site under different folders basically the intent is to restructure the existing site which is already in production.
Could anyone tell me how do we go about it?
Instead of writing a custom "one-time-use" tool for this, I would recommend you to get advantage of a standard "Transfer Items" application. You can find it in Sitecore Control Panel: go to Database > Transfer Items to Another Database.
So, what you basically need to do:
plug in the master database from the target new site to this older site, like "master_new" or something. This will require the web.config modification. The section on SDN about publishing targets should have a guideline how to do this
run the "Transfer Items" application, select the templates / layouts you needs on the first page, select this "master_new" database as a target database and the place in the content tree to transfer to on the second one
run the actual transfer
If your layouts / templates are groups into folders, this process will take the minimal time - much less comparing to creating your custom script...
UPDATE: Some sample code how to trigger this application programmatically:
UrlString url = new UrlString(UIUtil.GetUri("control:TransferToDatabase"));
Context.ClientPage.ClientResponse.ShowModalDialog(url.ToString());
I would look into using Sitecore Powershell Extensions (look at marketplace). It is a perfect fit for a usecase like this.