I try to add a custom connect with this article and it's working perfectly.
https://www.docusign.com/blog/developers/common-api-tasks-add-custom-connect-configuration-programmatically
I can't find the 'Status' property in the documentation
https://developers.docusign.com/docs/esign-rest-api/reference/connect/connectconfigurations/create/
How can I Activate programmatically this custom configuration ?
Set the allowEnvelopePublish attribute to true to turn on the configuration.
You're absolutely right that a better name for that attribute would have been enabled or somesuch.
Thank you for programmatically creating Connect configurations. It gives a much better user experience for the admin when your application takes care of the task.
Related
when creating a Windows Server on Azure, the user is given the option either to buy/rent a server license or to use his current windows server license if he's got one. (‘Already have a windows server license? Yes, No’).
As the administrator/owner of a subscription, I would like that my users to not see this option when creating a windows server. In other words, I would like to deactivate this option.
Could someone in the community know how to get this done?
P.S I'm new to stackoverflow and that's why I'm not yet allowed to insert pictures.
Thank you in advance!
Regards,
The Learner
You can't disable this option in the UI, but it is possible to create a policy that will block the creation of VM with HUB enabled.
Look at the Microsoft.Compute/licenseType alias, you need to create an ARM policy on it. Documentation is here.
I'm using a 3CX v12 phone system and I would like to add to the Snom 300 provisioning template so that the Cancel button is mapped to RETRIEVE. From the web interface of the phone I can see that the setting is for "idle_cancel_key_action!: keyevent" and I'd like to change it to "F_RETRIEVE" in the provisioning template. But when I look at the current template in order to edit it, I don't see where that setting is.
I can change it on each phone using the web interface, but I'd like to automate it using the provisioning template.
What can I add to the template so that this is done during provisioning, and where in the template do I add it?
I figured it out. I added this at the bottom (but still inside) the phone-settings tag:
<idle_cancel_key_action perm="">keyevent F_RETRIEVE</idle_cancel_key_action>
That worked perfectly. I hope this may help others in the future.
Jono
How it is possible to change Property of NT Service dynamically. I am using Installscript Based Project and installshield vesion is 11. I want to change NT Service property "Allow to interact with Desktop" dynamically based on certain condition.
I have tried to write custom action whose sequence is between InstallService and StartServices. This custom action is changing registry value "Type" of service. Is it a proper solution?
Regards
Dev
Since you asked if it's a "proper" solution I'll assume you are willing to listen to some advice. Generally speaking it's a really bad idea ( nor best practice ) to create a service that can interact with the desktop. This is especially true if the service is elevated as SYSTEM as it just open up a huge actack surface.
The generally accepted best practice is to split your UI out into it's own application such as a tray app that gets autostarted and code this UI to communicate with the service component. An example of this would be if the service created a WCF endpoint that exposed an API. This allows you to sandbox/firewall the elevated process and expose only those capabilities that are needed by the user.
If your development organization chooses to ignore all of this advice then form an installer perspective what you are doing will work but is not the optimal design. A better design would be a custom action that modifies the ServiceInstall table at install time to change the value of the ServiceType column so that when InstallServices run it is already configured correctly.
I have a task at hand where I need to add an attribute (Home Page) to user model without making changes in liferay source code i.e. modifying the service.xml and regenerating the service.
I searched a lot on this but nothing seems to work. Used hook to override the create account page and all. Does anyone has step by step solution for this?
Only the steps will do as I just need guidance on this.
Thanks
Mohit
I think you should be able to add custom attributes just by using the control panel.
This link should give you an idea.
I am currently working on a custom SharePoint web part (WSS 3.0, not MOSS) that will pull in information for all of the users in Active Directory to build an up to date employee directory. This web part shows things like phone number, address, and other similar fields. The issue that I am having is that, by default, the SharePoint web site on IIS is running as the user IUSR_. This user does not have access to Active Directory, so I am unable to retrieve any user information.
To get around this for testing I have hard coded the credentials for a test user which I added just for this purpose. This, obviously, is not ideal. If anyone removes this user or if they ever change the password then the web part will break and they will have no way to fix it (they have no in-house developers to take it over once I am finished here). To fix this problem, I would like to make the Username/Password custom properties on the web part so I can pass those to Active Directory to retrieve the information I need. The issue I am having with this is that the password is stored in plain text so anyone can read it. I would like it to display as ******** or something similar. Is there a way to make a custom property on a web part a password type?
If this isn't possible, can anyone recommend another way to accomplish what I am trying to do? At this time I cannot change the user that the SharePoint website runs as. Although, if I cannot find any other solutions I will try again to persuade them.
Thanks in advance!
We use a service account for that. That service account is solely used for that. Something like DOMAIN\SPS_AD_READ_CUSTOMER
In our documentation that we deliver when putting the application in production that account is put in the list of stuff that is needed to make the webpart run. If the webpart ever fails, the ITPro can go to the chapter and check if everything is still ok.
It's not ideal, but I don't really know another way on how to fix it.
I would go with custom Editor Part, then set up a control of TextBox with property TextBoxMode set to Password, then override methods from type EditorPart - SynchChanges() and ApplyChanges() to set and retrieve values.
tip: override method CreateEditorParts of a WebPart type to start with.