I need to have separate template at each folder level ,not at project level.
Lets say in details tab I have 10 fields in one folder and I need only fields in another folder in the same project.
Please let me know if this is possible with Workflow or any other way.
Thanks,
Ms
In HPALM, test folder is not part of entity structure framework. Hence you won't be able to setup custom fields at this level. Workflow customization will not help here.
Related
I want to create a Project Dashboard using 'Sharepoint List', for this purpose i need to have certain Project Level fields to be added to my list to show data. Is there any possibility i can get project level fields in my task list or a custom list?
I am using Project Online.
Regards
There is no direct way in SharePoint Online to read the value of "Project Level" from Project Online into a lookup field in SharePoint list.
As the title says...
I've successfully got workflows working that create project tasks, so I have some idea how the workflow customization tools work. But I'm struggling to see how I can (or even if I can) use a workflow to auto-magically add resources to the project (and then assign them to the project tasks I dynamically create.
Regarding which users/employees to add as resources, I imagine sorting out an appropriate clause shouldn't be too hard.
If I recall correctly, Resouces on a Project record are sublists. If I am correct, then it is not possible via workflows. There is a limitation with Workflows that they cannot work on record sublists.
You will have to do this via SuiteScript.
In my solution I have a workflow where one step contains a reference to Queue. After importing this solution on another CRM instance this workflow could not be activated because it contains an invalid reference - Queue can not be resolved. Queue with same name is created on new CRM but resolving is probably based on record Guid.
Now, I'm wondering, is there a way to edit workflow steps using CRM SDK? Whole process of CRM solution deployment is automated. And I want to remove all manual work. Some example would be great :)
Thanx in advance!
There are 2 things you can do if you are having issues with the Guids not matching in a workflow lookup when deploying from one environment to another.
Use the API to create those records referenced in the WF. When you create a record you can actually specify the Guid that it uses as the id. So write a tool or see if one exists already that will create some default data for your environment.
Use a configuration entity with references to all the EntityRefrences needed in your WFs. Then you can create a custom workflow activity to retrieve the configuration entity record (there should only ever really be one) that contains all the references in that environment.
I need to transfer a reusable Workflow from the stage env. to the prod.
The workflow is associate to a list, so the list id is stored in the workflow.
Is it possible to transfer the workflow and change the list id to the list name with Visual Studio? (We have no SharePoint Designer access to the prod. env.)
Short answer: No
I tried several hours to fix a reusable workflow, which same as yours was associated with a specific list - I switched systems and the GUID changed --> Workflow was broken.
You can give it a try and rename the MyWorkflow.wsp to MyWorkflow.cab and extract that somewhere. The workflow files are XML based hence you can edit the associated list GUID with your favorite editor. Now you need to package your edited file back into a cab file, rename it to wsp and you can give it a shot. I tried exactly that and resented to just "re-clicking" (as it's SPD) my workflow (two screens come in handy here).
That's what I call "reusable" workflow... Next time do not associate your reusable workflow with anything to keep it reusable.
I would recommend creating an Content Type in a Feature and then base your list and your Reusable Workflow association on that Content Type. We had a project in December where we successfully used this method. I saved a Reusable Workflow as a template. I then deployed the Content Type solution package and the Workflow solution package to another environment. Worked like a charm.
There are tow alternatives for deploying workflow regardless the assigned content types
It is very simple just do the following:
Alternative One
Save the workflow as template
Go to the following path in your site
http://your_server_Address/SiteAssets/Forms/AllItems.aspx
Download the file as WSP
Go to the following URL
http://your_Target_server_Address/_catalogs/solutions/Forms/AllItems.aspx
Upload the WSP, and activate the solution
Go to the site settings, then Site Actions, then Manage site features
Activate the feature that is related to the workflow
If you click workflows under site administration you would be able to see your custom reusable workflow
Alternative Two
Save the workflow as template
Go to the following path in your site
http://your_server_Address/SiteAssets/Forms/AllItems.aspx
Download the file as WSP
Open your visual studio
Click add new project
Under SharePoint choose 2010
Choose Import reusable work flow
Follow the wizard
Project will be created and can be deployed
Note : Make sure your workflow is reusable and that it has no errors
I'm looking for a way to localize SharePoint 2010 Folder Names, for a specific application.
I've seen that site names/description are automatically translated, and it seems like SharePoint 2010 supports "multilingual" fields for metadata - but I haven't been able to apply this successfully for folder names.
The folders are automatically generated, and the number of folder is limited (so I'm not looking at providing the users a way to translate their folder names, but a way to localize a predefined folder structure).
In a nutshell :
- is there a way to localize folder names ?
- if yes, is what's the best way to deploy this as part of a solution ?
Have you considered how Managed Metadata might be able to help you with this? If you're able to control terms that are also localized in Taxonomy, perhaps when creating a folder you would pull from the Managed Metadata Store, and then display the appropriate language based on the user's language setting. Just a thought... Since you know the name of the folder ahead of time, you could use that as a label for a folder name term, and then pull another label that matches the user's language and display that.
You can start using a resource files in your project and this link can help you about it.
But if you want to let the user, who creates a folder to set its localized name; then you should consider using SP event receivers.
I hope I've understood you correctly.