I have mistakenly used a wrong link module between module A and B. I now changed the link module to the correct one, but the previously created links remain assigned to the previous link module. How can I change all at once to the new link module?
if you only have a few links/modules to be corrected, follow IBMs advise at https://www.ibm.com/support/pages/how-move-links-between-link-modules-manually-without-using-dxl
insert a traceability column
convert layout column to DXL attribute
Use 'Link by attribute' to create links with the new link module
delete old links
Otherwise you will have to create a DXL script which iterates over the modules, objects and links and creates new links and deletes old links
Related
Hi want to insert a few hyperlinks in captivate 6 slides. However, while doing the development of the project, these links point to a test server. I would like to replace the base part of the hyperlinks , the www.abc.com part with the new destination address, once the project is to be final. Is there a way to use variable or some other method to do this in captivate , where I create part of the hyperlink with a variable, and just by changing the variable value , have the hyperlink in all the slides change ? Thanks.
I'm not at a machine with Captivate installed so I can't verify this works, but if you put the base URL in a variable called base, you might be able to set the destination address to $$base$$/location/of/resource
For future reference, a fairly active forum for Captivate exists on Adobe's site here.
I added a link-type with Forward=Task and Reverse=User Story using a Dependency. I uploaded this to my collection successfully.
Now I delete the link type and upload the template successfully again.
When I now want to create a new link type containing "Task" as Forward I get the error:
TF201006: The link type NEWNAME conflicts with link type OLDNAME. The name Task is already being used. (type ProvisionValidationException)
I don't see how to remove the OLDNAME.xml on my TFS because I don't know, where those uploaded templates are stored. Obviously the ProcessEditor will leave those files even if you remove a link type.
I got it. The LinkTypes are uploaded as entries in the LinkTypes-table on the SQL-Server-Database responsible for the team collection you upload the template to. So if you experience the same problems go ahead and delete all items from this table which are added by yourself.
I am using Web Part Connections to filter documents in a documents library in SharePoint. To do this, there's a column that is required, which I've named "related contact." Here's my problem: When I go add a New Folder (instead of just a document) SharePoint only asks me for a title for the Folder. The "related contact" column (which is required for the documents) doesn't even appear. Since the info on that column is empty, web part connections doesn't see the folder at all. Is there any way to make the Folder ask for another field at the time of creation?
Thanks
-V
Did you try creating a new folder content type with those required fields and trying to use that (and perhaps turn off the standard folders)?
Perhaps this page will help you: SharePoint folders and metadata.
Folders are one-dimensional. They are virtual containers for your documents, but aren't objects in your library that contain actual metadata.
Instead of using folders, I would recommend adding a column to your library that would mimic the names of the folders. From there, you can sort/filter/group/query the contents of that library. If users are sticklers for the folder structure, you could create a View that groups the documents by that new column, which would give you the appearance of folders.
I'm trying to add some Markdown capabilities to my Symfony project (Symfony version 1.3.3).
To accomplish that, I had already included the Markdown library into lib/vendor directory. Also, I added the need configuration in the autoload.yml for the previous library.
However, I'm getting a fatal PHP error:
Call to undefined function Markdown()
How can I resolve this problem?
The symfony autoloader loads classes from php files named like <classname>.class.php. If you're using the markdown.php file from mitchelf.com, it does not follow the naming scheme, nor does it contain a class called Markdown, as a matter of fact: it has a function called Markdown.
Symfony isn't even trying to load it, for reasons I described above. You will have to include it manually. I suggest you have a look at http://www.symfony-project.org/plugins/sfEasyMarkdownPlugin.
I do NOT suggest installing a plugin for such a simple feature. It is not hard for you to figure it out if you have some real examples.
There is an open source project based on symfony named Bookeet. It has embedded MarkDowm feature. It uses markitup as the markdown editor. And it uses php markdown to convert markdown code to html code.
To save your time, go directly to changeset 29f0ba1807 of the Bookeet project(I am sorry that I can't post the hyperlink because SO doesn't permit new user to post more than one hyperlink). You could see clearly what should be done in order to add markdown feature to your website.
How do I get an existing Document Type to show up in the Create dialogue of Umbraco 4.
I installed the BlogForUmbraco4_1.0.0 package, which I realize tries to install as the primary site, but it also installs all of the necessary Document Types, including Blog, and BlogPost. Why are they not an option when creating a new item within my site.
Umbraco uses a permission based Document Type Hierarchy, to ensure that editors doesn't create weird page types in wrong places (like a 'Homepage' beneath a blog or a 'News Item' inside a Gallery).
So you'll need to allow the Document Type that you wish to appear in your create dialog to the Document Type of the page you're using as the parent (this might sound like non sense ;-)).
So, say that you've imported the Blog4Umbraco package and wants to allow a blog below a Home page, you should find out which Document Type that home page is (look at the properties tab on the document and look at the 'Document Type').
Go to settings section and open Document types and click on that doc type (let's just say it's called 'Homepage')
Click on the 'Structure' tab and you'll see a list of all Document Types in your install. Some of them are already checked and those are the ones that are allowed beneath that type. To allow blogs, simply check the 'Blog' document type as well :-)