The Docusign "Switch to New" from classic view is not taking any template changes that are made using the new view.
I have modified the template fields using the same account, still i am unable to see the changes reflected using the new view.
However if i use the classc view and am making any changes the template changes are visible.
Please suggest.
Yes, The template changes done in the new experience is not reflecting at all. It is saying no permission, but I am able to modify the template using the classic view.
I think it works for simple templates but does not work in case there is heavy configuration done on the template using the docusign preferences menu where the signature and css are being modified.
Related
I need to create few templates for E-commerce site. Can anyone guide me as how to create templates in Kentico 9 ? There is an existing site and I need to create five other templates for the same. Am totally new to Kentico.
Please help.
There are many generic templates in Kentico, so you could clone any of them and modify to your needs - this might be easier for you to edit existing one as you'll have an example.
I'd recommend you to take following steps:
Go to Pages application in Kentico administration
Select any page in content tree on the left
go to properties -> template
Save as new template (so you do not screw up exting one) and save your changes
Switch to Design tab - this is where you build/configure you template
On the Design tab there is green line with template name and hamburger menu, where you can choose edit layout - this is where you can implement markup of the page as well as split your page into zones. After you accomplish html for you page save changes and close current dialog.
Now you should be back to Design tab. Here you can add web parts to zones you've specified in the layout. There is huge amount of different web parts (user controls). All they have different purpose and settings, so you should check documentation and figure out which one should be used in your particular case.
Try editable text, editable image, repeater, navigation in order to get an idea how it works.
I have a sharepoint solution package with a Custom UserControl inside. When I deploy the .wsp the user control is placed in the CONTROLTEMPLATES directory. Is there any way to "delay" this step until feature is activated?
In other words what I would like my custom user control to be available only after the feature is activated.
As far as I know this is not possible. On deploy all the needed files are copied to the correct location. It is actually feature independant, because you don't even need a feature to deploy files. You will see that a feature is automatically created when you for ex. add a webpart to your solution. Not when you add a mapped folder.
What are you trying to achieve with delaying the usercontrol? What you can do is check in your usercontrol if a certain feature is active and adapt the rendering of your usercontrol accordingly. Ex. Show message that the feature should be activated before using the control.
I have a document library with 4 content types, each having a default template. Users click on "New" and choose the content type for the new item.
I need WSS 3.0 to create a copy of that template (in the current folder) so that the users can edit it. I do not want WSS to open the template in a client application -I need it to leave the template right there.
How could I accomplish this?
Thank you for your help.
I wonder what you mean by EDIT the template copy, you mean setting properties? cause otherwise you must open it in a client app.
Anyway, we did t before for a client, he needed a file naming convention feature, so we added a feature that replaced the New button options with our own option, that takes the user to our custom page, where he selects the content type and fill in appropriate metadata. When clicking OK, the template is copied to the folder, given name according to the convention and assigned metadata. After that we opened the file in a client app, but you don't have to do that. The whole thing involved
Feature XML files
Layouts custom page with code behind
Custom menu customizer code to hide the New button options
Hope it helps
I want to create a custom new item page for sharepoint but there are two approached that I
can use and I want to share your experience in determining which is better.
The first: is to create a page in a library then create a C# library project to handle
the events of the controls on the page.
The second: is to define a feature of the content type of my list and specify the new
item form to be my custom form, then create a website containing the custom form and put
this site at the layouts folder.
for me the first approach is fine but the problem is that a user may access the default
sharepoint new item form which I don't want to happen.
but I don't like the idea of placing the form in a library on the site.
so which is better in your opinion ?
thanks
i suggest you to go with your second approach ...
Create a completely new feature that allows you add your functionalty of page creation and any customization realted to that and deploy this one to the 12 hive features folder as a new feature and every time you want have such a page created you can you this template and create the page...
Well, frankly, I'm confused by both of your suggestions.
I don't see how the first one would ever work.
And the second one; you don't "put sites in the layouts folder".
Here's what I would suggest you to do:
Download and install the WSS Extensions for Visual Studio.
Create a List Definition using these new templates.
Copy the NewForm.aspx from the 12 hive and Customize it.
Download and install the WSP Builder from Codeplex.com
Add your custom list definitions and files to a new Feature project in WSP Builder.
Package the Feature up to a .wsp using WSP Builder and you are good to go.
Your custom page(s) should be placed in your custom folders in my opinion.
Hope this helps.
Your concern in the first approach is that people will still be able to access the default form. If you are not opposed to using a custom control template for a content type definition, I recommend creating a very simple redirect control template and assigning it to the content type's "New Form". Such a control template need only contain one custom control, which has an OnInit or OnLoad method that contains little more than a Page.Response.Redirect call. Make that redirect point to the page you create in your first approach, and now whenever anyone tries to access the default new form for that content type, they will instead be directed to your custom page with all of your custom code. It is perhaps a bit of a hack, but it's definitely functional.
I am trying to add a view to a custom list. The target is MOSS 2007, I am using VS2008 w/ VSeWSS 1.3. The feature already has a custom list definition, including a custom view called "Calendar". To get started I thought I'd create another view called NewCalendar that is simply a duplicate of the existing custom view Calendar.
So, I copied Calendar.aspx to NewCalendar.aspx, copied the existing "View" node for the current calendar and pasted a new node, then changed the following attributes of the new node: DisplayName, Url, and DefaultView.
When I refresh WSP View NewCalendar.aspx shows up. When I deploy and go to NewCalendar.aspx i get a 404. Using SharePoint Manager I confirm the page is not present.
How do I add a custom view via a feature so that it shows up in the "View" drop-down?
UPDATE: It works if I create a new instance of my custom list. How do I get the custom view to show up on existing lists?
Unfortunately features in general are not retroactive. You cannot update a feature and expect all existing items that were created from that feature to be updated. This i assume is by design. If this were possible it could potentially have far reaching (unexpected) consequences.
In these senario's i script out a retrofit script, when publishing the new feature.