For each model element, there is the option in EA 10 to create internal requirements, constraints and scenarios. All of them end up in reports if you use the pre-defined Basic Template.
However, if you select "structured specification" instead of the default "description" text field for a scenario, then I end up with the steps of the structured specification being ignored in the report output.
How can I have them included in reports?
It sounds like you need to create your own reporting template. This may seem a bit daunting first time out and the template editor is pretty ornery, but luckily you can use an existing template as a starting point.
Hit F8 to bring up the Generate Documentation dialog, then select the Templates tab. Click New, specify a name and select a template you like to be copied. Don't bother with a template group, and leave the fragment checkbox unchecked.
In the editor, scroll down about halfway (assuming you selected to copy the Basic template) and locate the yellow scenario > tag.
Now in the checkbox tree on the left, scroll down do Package - Element - Scenario. Note that Scenario is checked, but Structured Scenarios is not. Check it.
In the editor, note the new structured scenarios > tag. Remove the right-click-to-insert text, then right-click and select Insert Field, then State etc.
It's more than a little fiddly, but if the Basic template is good enough to begin with you should be able to add the structured scenarios with a minimum of effort.
For more information, see the help file under Reporting - RTF Documents. Note that the individual fields aren't listed in the help file, you need to open up the template editor to see what specific information you can extract to your report.
Related
On JIRA tickets I can format comments entries at will : there's a toolbar with many choices for that, color, styles, underline...
But how do I get the same for description field ("descriptif" in French)?
Because what people read for explanation of a story/task/ticket, is mainly this content.
And currently the only thing we can do is to write on some descriptions "Look at comments to learn the purpose of this item/understand something" because a plain text is sometimes not enough to explain things.
This can be handled with renderers under Field Configuration Scheme.
Open Project settings -> Field Configuration.
Find the field "Descriptif"
There should be a text called "Renderers", click that. (In some version, it may be inside Edit)
Select "Wiki-style Renderer"
Click "Update" button.
And voila, it should be formatted like the Comment field.
Also, for further info you can check following Atlassian documentation.
I have access to the Navision SQL Server database and the corresponding Microsoft Dynamics NAV interface.
I want to migrate the 'Aged Acc. Receivable DII' report. Once I select the report and go to Tools > Designer I can see the 'DataItem' list, and when I select any of those and press F9 I see the C/AL Editor as per below.
Selecting another 'Data Item' provides another code. My initial question would be, which code from the 'Data Item' refers to the 'Preview' button in the 'Aged Accounts Receivable - IRES' window?
From the code I understand there are 3 tables joined (Customer, Cust_ Ledger Entry and Detailed Cust_ Ledg_ Entry) but I can not manage to output the same result that in the report produced in the interface. I'm guessing this is a generic report. Is there a query that could be used to generate the same output? Or documentation that would explain how the report is created?
Oh man, i don’t know where to start. MS seems to finally buried Navision 5 along with it’s documentation on msdn. But it is still should be possible for you to open local documentation with F1. Just make sure you are pressing it while your input cursor is on the code. This will open developer’s docu. You will not find there any explanations about how data is structured for output, but you will be able to find how things works.
Back to your questions. You need all the code you see in triggers. And might happen you will need code from the layout that you have not yet discovered. Preview and print buttons doing the same except for the global variable CurrReport.Preview is set to true.
To see if there is any other code open View-Sections, select any section and F9. Code will also be different per section.
The form you are asking is called RequestForm, hence the menu called View-Request page. F9 on the page and any elements on it.
Also, see the button that is third from the right on toolbar on your screen. That is Properties. Many things have properties. For example DataItem’s properties will tell you have child and parent are linked.
If you can open report in the designer then you probably have a developer’s license uploaded to database. Where is the developer then?) It should also allow you to export objects to text file. The you will be able to read every last bit of the code. When window with dataitems is active (for previously mentioned commands as well) press File-Export and select text format. Fob will produce binary output, not useful for you.
I use the search in JIRA about 50 times a day and every time it forgets what I just entered. Is there any way to tell it to remember the last search or the project code. (By project code I mean the first few letters of bug code such as "AAQT-").
That prefix is known as the project key.
(Also, what version of JIRA are you using? There are some UI differences between Cloud and most Server instances so my following advice might not make sense.)
There isn't a way to pre-define the project key in the quick search box since most JIRA instances have multiple projects, and pre-defining it for just one project doesn't make sense.
However, your browser should be able to remember previous values entered. You would have to overwrite the numerical portion that follows the key, though.
Do you mean save your search as your favourite filter? If so then you can follow these steps :
Click on "Issues" dropdown then choose "Search for issues"
Click on "New filter" button on the top-left area
Type your query
Click on "Save as" button on the above of query field
Give any search name, then it will be save under "Favourite Filters" section
I know StructuredSelection will be used when you select a file in Package Explorer for example, and TextSelection will be used when you select some text in Editor, but not clear about MarkSelection, when it will be used?
MarkSelection is generated by TextViewer (so usually a text editor) and reports a change to a 'mark' selection. It will only be sent to selection change listeners for the text viewer.
The TextViewer.setMark method causes the mark selection changed event to be generated. This only seems to be used by incremental search and for marked regions used in Emacs style editing.
Ektron 9 - steps to trigger issue ... we think:
Create new content folder
Edit folder properties
Smart Forms tab - untick inherit, and remove "Blank HTML"
The "new" menu on the folder now:
Does not show DMS Document as a menu item
Does not show Smart Form list as a pull-out sub menu.
Question
How do I get "Blank HTML" back into the smart form tab property in the folder
Why is this happening
Help!!
[Edited] Workaround
eGandalf gave the simple answer via Twitter (previously I had attempted a workaround of putting inheritance back on then resetting the tree): toggle the "Require Smart Forms" checkbox on the "Smart Forms" tab and the Blank HTML option will come back.
This is by design. When you remove the HTML option, note that it checks the "Require Smart Form" box (and, reciprocally, checking the Require Smart Form box removes the HTML option). That means that all other types, including PageBuilder, DMS documents, or HTML are now forbidden in this folder.
As a best practice, you shouldn't be mixing types in a folder anyway. A lot of people do, but that doesn't make it any more valid. If you've got a folder for Press Releases and you have a Press Release Smart Form, you shouldn't have any other type of content in that folder. The less you mix types, the less filtering you have to do either with the API or post-request via LINQ. As a result, you'll have a more consistently performing site.
In situations like this, where I want the DMS assets and the Smart Form content to a) both be searchable, b) both be managed by the same user/group and c) there's a strong connection between the two (e.g., Whitepaper information Smart Form + PDF asset download), I'll create a child folder and allow DMS assets there. In the Case Study example, the folder structure may look like this:
Content
Case Studies (Smart Form only)
Downloads (DMS Allowed)
In contrast, if I don't want the DMS assets to be independently searchable, I'll remove them from the Content folder entirely and place them in a separate, root-level, non-searchable folder called Resources or Downloads.
Because Blank HTML is a default (and ID 0), you might have to reassign it in the database.
My guess is that removing the Blank HTML option impacts DMS retrieval in the workarea specifically.
In this case, I'd reach out to support, I've never actually needed/wanted to do this.
Edit:
I dug a bit more to try and give you something to try.
You'll need to reinsert an xml_id into folder_to_xml_tbl.
insert into folder_to_xml_tbl VALUES(your_folder_id, 0, 1);
Ektron support have replied:
Hi ,
Engineering have advised that DMS documents are unstructured.
By forcing all content to be structured content, it disallows raw html as well as dms assets and only allows documents with structure to be created
In any reply please include the case number in the subject line.
To open a new case email uksupport#ektron.com or use the support request form at http://www.ektron.com/Resources/Support/Contact/