Is there any way to export workflow templates (and then import them into another CRM)? I exported all my workflows, but the templates were not among them. I'm not seeing how this is done.
Thanks!
It looks like there is no direct way to export a Workflow template. In order to export it, you will have to turn it into a regular Workflow. After importing in the destination CRM, you can edit it and change it back to a template before publishing.
Would this be an acceptable workaround in your scenary?
Related
Is there a way to rename a Variable or Variable Group without breaking the references it already have in Tibco Business Works 5.x. Thanks.
A way you could do this is by editing the complete source code that is in XML. After taking a proper backup.
You could identify the variable or variable group XML tags to be renamed and rename them by using an advanced text editor with Regular expressions if is the case.
Once you rename everything you would have to open TIBCO Designer and go to the root location of the project and validate All. Validate the complete project.
A manual cleanup and re-built, testing would be required.
Avoiding changes in a massive scale is advised. Less Risk.
We are studying on Oracle Data Integrator and we want to move our ODI project from one pc to another. Both computers are identical. we managed to export project via OdiExportWork from Designer as in .rar file format. But we could not managed to import it. How can we do that?
Any kind of help is welcome.
Regards.
Actually you are able to export as XML file. You may do it as folder by folder or interface by interface or you may export/import whole project.
Just right click on the object you want to export and then select an export location, carry the XML file to the new computer then import it into your workspace.
Latest version of ODI studio has ability to export/import project, model, related knowledge module etc at one go.
This feature is named as smart export /import. It comes from version 11.1.6.0.
Looking at https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSAttributedString_AppKitAdditions/Reference/Reference.html, there are quite a few document formats that AppKit makes it easy to export to, including even MS Word. It seems strange that Apple wouldn't also provide easy export functionality like this for their own word processing software.
Am I missing something in the documentation? Or should this be done using some other set of tools? I know I could export to pretty much any of those other formats and Pages would import it, but it would be nice to export directly to that format.
Alternatively, if there's a specification out there that would help in developing an export method like the ones above, that would also be useful.
Or should I be looking into AppleScript hooks to do this sort of thing?
No, you are not missing anything. There is no API to programmatically create Pages files and no public spec for the format. Unless there is specific reason you need Pages files, your best bet is to create RTF files. You can write code to create formatted RTF files, and Pages will open them and you'll see the correct formatting.
I have created a Silverlight class library which holds a lot of the common utility methods I use day to day in my Silverlight development.
I am starting to play around with Workflow and would like to reuse this common dll. After referencing this dll in my workflow project I see a yellow warning icon beside it.
I can use the functionality from this dll when creating ‘Code Activities’ without issue. After adding the using statement for it all works AOK.
using EquinoxeAISManagementSystem.Common.Helpers;
BUT when I try to import the dll from the activity designer, I do not see the dll in the import window.
If I edit the XAML and add it directly, I get a warning.
Is it possible to reuse Silverlight dlls?
I believe I can answer my own question.
The project EquinoxeAISMAnagementSsystem.Common is part of another solution. I had added this single project for the other solution into my new workflow solution (which I was having this issue in).
When I added the reference to the EquinoxeAISMAnagementSsystem.Common.dll initilly, it was by referencing the project in the workflow solution.
This seems to be the cause of the issue (for workflow anyway).
I was able to correct this issue by adding the EquinoxeAISMAnagementSsystem.Common.dll to a common folder where I keep all my external dlls (for ease of use).
..\Projects\EquinoxeAISManagementSystem.DLL\
I set up the output destination folder for this EquinoxeAISMAnagementSsystem.Common project to the folder above. I was then able to add the reference to Common.dll by browsing directly to the folder above.
Hay presto, all works.
I’m not sure id this is the ‘correct’ way to do things, but I needed to get over this hump.
I would be interested in anyone’s comments and if there is a correct(er), why to fix this issue.
Thanks ….
I want to create a template kind of thing where there will be more than one project in the solution. Like one test project + one normal project + some other project.
How to do that.
When I export a template it exports only one project.
We had to resort to a powershell script to do this, as we couldn't find a reliable way of doing this.
This is fully supported but you'll need to modify the .vstemplate file manually. Starting by running the Save as Template on each project is a good first step. Now you need to bind them together in another .vstemplate. More information can be found here:
http://msdn.microsoft.com/en-us/library/ms185308(v=vs.80).aspx
Have you tried this: http://visualstudiogallery.msdn.microsoft.com/57320b20-34a2-42e4-b97e-e615c71aca24