Am wondering whats the use of supporting multiple output schema as shown below in the image?
I was hoping to configure two different outputs from this DROP Field transform and in the subsequent child transform be able to select specific parent output schema as input. But i don't see that option at all, could someone help me understand the need of outputschema drop down and editing capabilities in the window(refer image)?
Thank you.
Related
I have a package with about 25 diagrams in it. I have used EA templates to make a package report that gives the name and notes for each diagram. However I want make a more specific report that can generates the report for just one diagram containing the description from each element in the diagram. Is this possible? It does not seem like diagrams have anywhere I can generate reports from.
UPDATE: I am currently trying to figure out how to do this with Document Options>Except where Query excludes Package:>Custom SQL but cannot get it. Here is my SQL statement:
SELECT t_diagram.ea_guid & t_diagram.Name AS [DesiredService-Hyperlink]
FROM t_diagram
WHERE t_diagram.Name = 'Diagram_Name'
I tried putting this in the Report's Custom SQL, that didn't work. Then I tried putting it in a fragment's Custom SQL with the following in the template itself
custom >
{DesiredService-Hyperlink}
< custom
This also did not work. I have been trying to go off of various documentation and YouTube Videos. If anyone could point me in the right direction that would be great.
Enterprise Architect document generation is based more on the model structure then on the diagrams.
The easiest approach would be to put each diagram in a different package or nested under a specific element, even if only temporary to generate the document.
I'd like to display the contents of a database table in a more interesting manner than just a table; different positioning, fonts, sizes, colours etc.
Is there a region type or plugin that can achieve that?
I tried the cards view but I it's still very limited (for example a minimum of 2 cards per row when I only need 1) Or maybe I should deploy it as a classic report and then use javascript to rearrange everything? edit: I also considered rendering the page with pl/sql and htp, but that seems overly complicated...
As I'm new to APEX, any input would be much appreciated!
You could do it as a classic report and change the template under the attributes to something else.
What I ended up doing was using an interactive report with a 'detail view'. That way you can use html+css and reference the data from the columns by using #column_name#. I'm really satisfied with it.
However the above answers are also very interesting! I definitely learned a lot experimenting with them.
I am Using Sitecore 6.6
I believe item:setdefaultworkflow and item:resetdefaultworkflow commands are used to reset the workflow fields on an Item with values set on Standard values.
If not please correct me.
Here is the Path in Core:
/sitecore/content/Applications/Content Editor/Ribbons/Chunks/Workflow/Set Default Workflow
commands are not shown on the Ribbon. How do I use these commands? what is their purpose. Any Help is greatly appreciated.
I am aware of Version >> Fields(Reset)>> then choose the fields to reset with multiple clicks.
I am trying to use these commands if they solve my purpose to reset the Workflow Fields to standard values with a command on Review Tab >> Workflow section with one Click.
As far as I'm aware, these buttons are only visible on __Standard Values items. They are used to assign the workflow that will be used for new versions of that template going forward, or to clear the workflow that has been set (note that items which are already part way through a workflow will still need to finish it before they are no longer associated with a workflow).
The idea is that you assign the workflow to the standard values of templates (or base templates) in your solution, and those settings then get carried through to your content items.
Although you are able to, I'd advise against fiddling with the workflow fields on individual items before you fully understand the purpose of the fields.
For more information, I'd suggest looking at the Sitecore workflow reference document: https://sdn.sitecore.net/upload/sitecore6/60/workflow_reference_sc60orlater-a4.pdf
I need to link 2 different dynamic fields in OTRS. What I have done till now:-
1 Created the ACL in Config file
2 Changed the customerticketmessage dtl for source binding
3 Changed the Agentcommonaction dtl
But the result is not reflected in customer webpage
I am now not really getting the way to implement it. Need help for it.
Thank You
What version of OTRS are you on?
Since OTRS 3.2 the Customer Interface supports ACLs: http://otrs.github.io/doc/manual/admin/3.3/en/html/otrs.html#idp9739616
Also, of course having to achieve your goal via ACLs is not that nice, the best way to go is to create a specific type of drop-down field with multiple levels. This would require some coding, though.
I was trying to move components in Page Editor mode , and below are the things I have done to achieve this :
Set Compatible rendering selected for the Sublayouts
Added placeholder settings and allowed controls for placeholders
But , when I was trying to move components, the DataSourceItems for the sublayouts are not changing , hence the content is not changing.
And , also sometime I am getting Field related errors if the fields are different in the DataSources.
Can someone please help me in this .
From your question, it sounds like you are trying to move a component from one placeholder to another in Page Editor. That does not affect the data source.
If instead you mean you are trying to personalize the experience by using rules to switch the data source within a sublayout, the steps you've taken won't allow for that. You need to add conditions to the sublayout in Page Editor to choose which data source you want to display.
If you are trying to have compatible renderings (different sublayouts) show for the same placeholder, that is something that is done by your step 1. This is only to help authors know what other sublayouts would be a good idea to put in that placeholder. It does not affect the data source.
When you add components, the datasource for them is not set automatically. You need to check if it's set and use Sitecore.Context.Item if it's not.
Not sure if that's what you mean..
As for field related errors, please post more details.