i have a usecase where i want to personalize the content, that a visitor see based on his
information saved in Audience Manager.(i have added a keyword "personalize" for one of the contact "x").For this
I have created a a target group, defined its characteristics and tracking keys(defined personalize > 0).
After this, i associated the Target group with a component presentation and Published the Page
When i logged in with "x" credentials i was unable to see that component presentation on the Page.
Please Help!
First steps:
Validate the user has the value for personalize in the Broker DB
Check you have the WAI module in your web app
Look at the published page, and validate the conditions are in the output
Check your target type is set to an appropriate language (not none)
Check your storage bindings are correct in Deployer and web app
If that reveals nothing, please update your post with more info.
Finally, consider posting this at: https://tridion.stackexchange.com/grant-beta-access?key=63880f9cbf452c62f726770209533893
Related
I want to set the dynamic deep link with query param. For example, Suppose I've got the following information, Let's say for user1 the URL is https://example.com/res/?appId=67abeuusbev&value=55673 this link will be dynamic. i.e. for user2 it can be https://example.com/res/?appId=67abeuusbev&value=55674. I've set up the Firebase dynamic link. For example, say exampletest.page.link/SYu7 . Now I want to set up the deeplink in such a way that those appId and value (https://example.com/res/?appId=67abeuusbev&value=55674) can be set dynamically as a deep link whenever this link will be clicked from a web browser and based on the respective param values I can handle the link. Is there any way to do the same in the firebase dynamic link? I'm using React Native. Thanks for the consideration in advance.
If you're looking into modify short Firebase Dynamic Links programmatically, then it's currently not possible. The only way to update the parameters configured (i.e. deep link) in a short FDL is through the Firebase console, and only short FDLs created from the console can be edited. Short FDLs created programmatically are not displayed in the FDL dashboard.
As a workaround, you can create long FDL manually - by appending parameters and its values. Note that deep links need to be URL-encoded if it has multiple parameters.
i.e. https://exampletest.page.link/?link=https%3A%2F%2Fexample.com%2Fres%2F%3FappId%3D67abeuusbev%26value%3D55674
You can check if the deep link will be able to carry the parameters configured in it by debugging the Dynamic Link using preview page flowchart.
I want to add the logs for the requirement history for the changes in the requirement tracebility. Currently,the logs for the changes in the requirement tracebilyt are not being captured in the history section.
Is any code or API to make changes in the requirement tracebility visible in the history tab?
thanks
History is not maintained for requirement traceability in QC. What you can do, enable history for comment field from customization and change your qc workflow script such that it adds comment (i.e. added link/removed link with ids) when somebody changes anything in requirement traceability section.
you have to make the Related field history enabled and to do so, you have to have administration rights on the project.
then go to Tools>Customization>Project Entities> Test Cases
then find your field in either the System Fields list or the User Fields list.
select the target field, in the RHS you will see the field properties and one of the properties is History Enabled. check that option and Save then Hit Return.
Log out of the project and re-Login.
now changes to that field will be tracked and appear in the History tab.
I have a Plone site configured with PloneFormGen. I'm using a save-data-to-content adapter to create a page for each submission, with a unique number for title/id. I have content rules set up so that various roles will be notified when a submitted form transitions along the workflow.
Is there any way to include the content of the submitted in these emails? I know PloneFormGen can send the content of the form in an initial email at submit time, but I need to send this same information later. I'm pretty good at figuring things out, but I'm no Plone expert so any help would be appreciated.
Additional info:
I'm using the uwosh.pfg.d2c adapter to perform the PFG -> Contenttype conversion, which works well. The content type is set to 'page' in the settings for the uwosh.pfg.d2c plugin. Content rules then will send emails to various groups or roles based on a state transition of the resulting content, which works in the normal way - when a transition occurs, the rule executes.
Effectively, what we have is pages that are being generated by the form when the user clicks submit. This is done through a plugin in PloneFormGen. This may provide some extra info: http://pythonhosted.org/uwosh.pfg.d2c/ - I'm not, admittedly, much of a developer.
Ideally, reviewers would get body-text of the created page when the form is submitted: this is done through a content rule that when a page is added to a folder, it sends the email. The page is added to the folder when the plugin in PloneFormGen creates the page.
When we have these pages, other users can come in and review and change the state of them - just as you can with any other page in Plone. PloneFormGen should have no further use once it's been converted to a page. Hope that helps.
The bad news is that this will require programming; the good news is that it won't take much. There are two reasonable approaches to solving the problem:
Have your content rule action run a script that handles the mailing itself. You can use the site's mailhost to send scripted mail; or,
In a Python package (no way to do this in a through-the-web script), provide a named adapter implementing plone.stringinterp.interfaces.IStringSubstitution for your context's text attribute. That will give you a $ substitution for the body. This would probably require less than 10 lines of total code.
You might want to have a look a collective.contentrules.mailtogroup, the newest version is capable to send the body-text as mail (use the '${text}'-variable), triggered on one of the convenient content-rules-events, in your case 'Object added'.
You can assign your roles to a group and use it for your case.
I am using SDL Tridion 2011 and need to take the permissions off from the user to localize a structure group so that he does not make any changes in the name of the structure group by localizing it. However, even after removing the rights and permissions and making the structure group ‘read only’, the user is still able to localize the structure group by right clicking on it and going to properties. Please help if there's any resolution for it.
Also, is there any way we can restrict the user from unpublising or updating a page?
Permissions on a structure group control what you can do to the things it contains. Remove the localize permission in the parent structure group instead.
To prevent unpublishing you can do any of the following:
Remove the Read permission.
Go to the Security tab in the properties of the relevant publication, and remove the right to Publish to Content Distributor
Go to the Security tab of the relevant Target Type, and remove the Use Target Type permission
To prevent them updating a page, remove the Write permission, although be aware that editing the page allows them to modify the page composition, and that controlling this doesn't prevent changes to the content if the person has permission to modify the relevant components.
If none of these is sufficient, then you will need to implement a custom solution with either the events system, or workflow.
Inspect the properties for your Structure Group and go to the Security tab. Check which users/groups have the localize right and then see if your user is a member of any of those groups. Groups can be members of other groups, so you may need to check recursively to find where this ability is being allowed from.
Also make sure that the user is not an Administrator.
To prevent a user from unpublishing a page then you need to make sure they do not have "Publish to Content Distributor" rights at the Publication level. If they need to be able to publish pages, but not unpublish, you will need to take care of that by writing an Event System.
To prevent them from updating a page, you need to consider the Write permissions on the containing Structure Group.
I'd like to use Elmah on my website except I'm concerned that if I get an exception on a page that accepts credit card numbers then people's credit card numbers will end up in the error log. Of course, I don't want a copy of them anywhere on my server.
So is it possible to hide the value of a form field on a particular page? For example, it would appear as txtBxCCNumber=xxxxxxxxxxxx in the Server Variable section.
First of all make sure you secure your Elmah logs from anonymous access.
Then, read the section on Error Filtering and the provided examples. You should be able to adapt an example on the page to filter out errors on your credit card form page.