I wanted to customize EDIT tab of publisher portal of wso2 registry. Currently we have below items:
Overview
Categorization
Contacts
Interface
Security
Doc links
Tags
Taxonomy
I want to add one more item under Categorization such as below:
"Classification" with drop down menu - vital, critical, discretionary
Please let me what to look for and where to look for in order to achieve this.
What you need to do is edit the relevant RXT and add a field element under the table categorization as follows
<field type="options" categorization="true">
<name label="Classification">Classification</name>
<values>
<value>Vital</value>
<value>Critical</value>
<value>Discretionary</value>
</values>
</field>
Please find the relevant documentation here to configure categorization options.
Related
Is it possible to change the name "Introduction" at the top of requests?
It's a documentation generated by Postman, i haven't access to the HTML code.
I need to change this name, does anyone know how I do it?
Those headings are created when you go through the +New > Documentation flow.
They can be changed/deleted from here when you first create the Documentation.
If the Documentation has already been created - You can change the headings by editing the Collection.
Once the Edit Collection modal is open, you will find the details under the Description tab.
I have created custom entities. I have set it in Sales. So, user can open it and use it. Ex. I have created new entity Purchase Order & Purchase Order Invoice. It shows default icon(Green) of CRM.
I want to change that icon and set my icon. Can anybody suggest me how to change the icon of Entity?
Please review following screenshot
If you are editing SiteMap xml manually there is an 'Icon' attribute in 'Subarea' node or if you are using XrmToolBox there is also an 'Icon' field that you cen set to your web resource.
I found this answer. It looks pretty easy and simple : https://community.dynamics.com/crm/f/117/t/213172
I have a Community Admin role, inherited by
sitecore\Sitecore Client Securing
sitecore\Sitecore Client Users
sitecore\Sitecore Client Publishing
sitecore\Sitecore Client Designing
sitecore\Sitecore Client Authoring
And I want to make quick info section visible to only Community Admins in Sitecore 8.
I tried using the checkbox Quick Info in Application options button in Top left corner of the content editor. This helps, but it is user specific that I can make this option show/hide to a particular user not for all the users who have Community Admin role.
How can I make this Quick Info section visible to all Community Admin users?
There is no user interface for specifying which users / roles can / cannot see Quick Info section. The only setting I am aware of is Sitecore top left (Hamburger) button --> Application options --> Content editor --> Quick info section; that is just a checkbox applied for currently logged user only.
Does custom code works out for you? There was a previous SO question on How to Hide Quick Info Programmatically
You can slightly modify the code from that post in order to check if user is in roles with Sitecore.Context.User.IsInRole method and that would work.
You Can also enable the quick info section by navigating to View -> Standard Fields and check the 'Standard Field' checkbox.See below screenshot.
I am working on Sitecore Item Web Api, I have a mulitisite solution and I want to give access of Sitecore Item web api to specific Site as per sitecore user.
For example, I have a demo site and have specific user for this site:
uname - test
pass - test123
My requirement is this user only can access given site via api not others Is it possible and how?
I am using http://sdn.sitecore.net/upload/sdn5/modules/sitecore%20item%20web%20api/sitecore_item_web_api_developer_guide_sc66-71-a4.pdf document and on page 13 it shows some extra fields for security "Field Remote Read" but in normal solution it's not showing any field like this
If you cannot see the field from the column list like #nsgocev stated, make sure that "Sitecore.ItemWebApi.config" is present in your include folder and enabled. This config adds the remote:fieldread field to the access rights/security editor.
<accessRights>
<rights>
<add name="remote:fieldread" comment="Field Read right for remoted clients." title="Field Remote Read"/>
</rights>
...
</accessRights>
Also make sure you set the correct mode to take this field into account (as stated in the documentation) to set up the API correctly.
<site name="website">
<patch:attribute name="itemwebapi.mode">AdvancedSecurity</patch:attribute>
<patch:attribute name="itemwebapi.access">ReadOnly</patch:attribute>
<patch:attribute name="itemwebapi.allowanonymousaccess">false</patch:attribute>
</site>
To display the Field Read Remote column you should enable it from the columns options from the ribbon:
And check the checkbox there:
Edited
The issue (#347688) has been fixed in Sitecore CMS 6.5.0 rev. 120427 (6.5.0 Update-4) and DMS 2.0.1 rev. 120427
We have been asked to explain where the editor can customize the campaign tracking url, they have seen the feature when participating in Sitecore Training sessions, but can't find the features in the our platform that is currently fully updated.
It seems to me the feature has been removed otherwise it is hidden in {3AC13180-912F-4388-AF56-46A0F1172E70} that is missing in the DMS Installation, when looking at the insert options for the Campaign Item.
Does anyone have insight on the topic ? and if the feature is still present or has been removed for another model.
OMS / Custom Campaign tracking URL
When looking at the old documentation for Sitecore OMS the section related OMS Creating Campaign Events, it should be possible for the Editor to personalize the incomming url parameter that triggers the page visit to attach to a specific campaign.
Reference: "OMS Creating Campaign Events" page 13-14
http://sdn.sitecore.net/upload/sitecore6/64/online%20marketing%20suite%20cookbook-usletter.pdf
Engagement Analytics / No Custom Campaign tracking URL (?)
In the new DMS 2.0 / Engagement Analytics there are also Page events, and they should be attachable to Campaigns. But we can't seem to create anything under the Campaign definition even tho the first line in the documentation suggests it. Looking at the Insert options on the campaign there is a missing id: {3AC13180-912F-4388-AF56-46A0F1172E70} that suggest the installation is missing an Item for this feature to function.
Reference: "Engagement Analytics Page Events" page 6-7
http://sdn.sitecore.net/upload/sitecore6/65/engagement_analytics_configuration_reference_sc65-usletter.pdf
Campaigns
You can associate events with specific campaigns. To register a
campaign event, beneath the campaign definition item, insert a
campaign event definition item using the System/Analytics/Campaign
data template. You can activate the campaign using the value of the
sc_camp query string parameter or you can assign a campaign to a
content item, such as a landing page. For more information about
campaigns, see the section Campaign. To change the name of the sc_camp
query string parameter, see the section The
Analytics.CampaignQueryStringKey Setting.
I have been in contact with Sitecore Support and they responded that the option of customizing the url that triggers the campaign has been removed. The documentation is misleading on the subject and they have registered it as a bug.
So yoursite.net/?sc_camp={ID of the campaign item here} or using a landing page with the campaign as trigger is currently the only way to monitor incoming links from a campaign, unless custom code is build.
Thanks for the answers.
Edited:
The issue (#347688) has been fixed in Sitecore CMS 6.5.0 rev. 120427 (6.5.0 Update-4) and DMS 2.0.1 rev. 120427
Mentioned ID {3AC13180-912F-4388-AF56-46A0F1172E70} used to be a Campaign Event template. Campaign Events are no longer used, as they were replaced by Campaign in Sitecore DMS.
In order to track it, use the following URL format: yoursite.net/?sc_camp={ID of the campaign item here}
I just wanted to add in that although it might be what they know and what they want to use, the reason that it's so obscured is because that's really not how you should be doing things and its not a practice I'd recommend since it's not really guaranteed to be tracked. The structure of DMS and the underlying database is such that I'd stick to setting things up by associating things with a campaign. Tracking is done in large part via page events that are triggered... but just amending a url will trigger a visit and a new page, but not a page event to be created unless there is something associated with that item that will trigger an event.
Campaigns are typically associated with items, or events, or engagement plans or any number of different elements of DMS. In all cases, there's a tab on the item that has an option to check the campaign to associate it with. That's how you want to be doing this which ensures that a page event is properly created and associated with the campaign.