Bonjour,
Lorsque je duplique un flux sous designer je ne peux pas affecter ce flux
à une autre liste. Y a t'il un moyen pour faire ça ?
Dans une flux j'ai une phase une trentaine de conditions et de mise à jour
de variables du flux et je voudrais éviter de ressaisir tout dans le
nouveau flux.
Merci
--
--------------------------
Merci
Sylfelin
Bonjour,
Lorsque je duplique un flux sous designer je ne peux pas affecter ce flux
à une autre liste. Y a t'il un moyen pour faire ça ?
Dans une flux j'ai une phase une trentaine de conditions et de mise à jour
de variables du flux et je voudrais éviter de ressaisir tout dans le
nouveau flux.
Merci
--
--------------------------
Merci
Sylfelin
Bonjour,
Lorsque je duplique un flux sous designer je ne peux pas affecter ce flux
à une autre liste. Y a t'il un moyen pour faire ça ?
Dans une flux j'ai une phase une trentaine de conditions et de mise à jour
de variables du flux et je voudrais éviter de ressaisir tout dans le
nouveau flux.
Merci
--
--------------------------
Merci
Sylfelin
Je l'ai fait en suivant ceci et cela fonctionne.
http://www.sharepointblogs.com/andynoon/archive/2007/09/18/reparenting-a-workflow-to-a-different-list.aspx
****
ci-dessous copie de la page web pour les archives si un jour elle
disparait
******************
Re-parenting a SharePoint Designer workflow to a different list
Before I start there is a good guide to transforming a SharePoint Designer
workflow to a visual studio .net workflow here: Porting SharePoint
Designer Workflows to Visual Studio. This will allow you to package a
workflow up as a feature and deploy and use it in multiple locations in
your farm. However for simple deployments you may want to stick with
SharePoint Designer, if you do - read on!
Within the same site:
So you've got a workflow and now you want to either move it to another
list or attach it to another list at the same time. The list you want to
attach it to is in the same site. You would think there was a way of
associated a workflow with more than one list but in fact there isn't and
to some degree it's understandable. A lot of the actions you define in
the workflow are specific to the library you are working with, even if you
were to abstract your logic away from the list then SharePoint Designer
links actions such as "Current Item" properties to the underlying list.
So, unfortunately it's not as easy as just editing the configuration XML
file:
[workflow name].xoml.wfconfig.xml
and pointing it at the XOML and RULES files for your existing workflow.
Your workflow will almost certainly contain references to the original
library or list, so just pointing the config file at you existing workflow
will have some pretty uncertain outcomes!
The good news is that you can use a lot of what you've already created and
apply it to a new workflow, as per...
Make sure the new list your working with is set up correctly (content
types, columns, approval, check in /out...)
In SharePoint Designer, create a blank workflow with a dummy step defined
Copy the contents of your original XOML file named, [workflow name].xoml
to the new XOML file that was created when you created the new workflow
(use notepad) NOTE: The XOML contains all the variables and activity
definitions for your workflow, but not the logic
Copy the rules [workflow name].xoml.rules file contents to the new rules
file NOTE: The rules file contains the login for if, then...else
comparisons
Compare your config [workflow name].xoml.wfconfig.xml file with the
original config file and make relevant changes (probably just need to
reference the content types created when requesting data from users)
Check through the workflow and change any fields linked back to the
original document library - THIS IS THE MOST LABORIOUS JOB!
UPDATE...ACTUALLY IT'S QUICKER AND EASIER TO OPEN THE XOML AND DO A GLOBAL
SEARCH AND REPLACE LOOKING FOR THE GUID OF THE ORIGINAL LIBRARY AND
REPLACING THAT WITH THE GUID OF YOUR NEW LIBRARY (GET THE GUID FROM THE
URL LINKS ON THE SETTINGS PAGES, THE "AUDIENCE TARGETING SETTING' LINK IS
PARTICULARLY HELPFUL!)
To a different site:
Your workflow is great and now everyone wants a go! You need to deploy
not just within the same site but to another location in your farm
The steps here are similar to the above, with the exception that you will
have to copy all the files that are required to run the original workflow
to the new location. These files are usually just the ASPX pages that are
run when you collect data from a user, you'll need to change the config
file to associate the workflow with the files in the new location. Better
still copy the files to a central location and reference them this
location in both workflow's. That way you only have one set of files to
keep up to date.
After you've done this you can follow the steps above to make the
necessary changes.
Neither of these approaches is really ideal and to be honest there should
be tools to make this process easier, you can kind of see from the
structure here that there is an app waiting to be written for this and if
I have the time maybe I'll put one together. In the meantime please feel
free to comment if you know of a simpler method.
Published Sep 18 2007, 11:40 AM by Andrew Noon
Filed under: MOSS 2007
--
--------------------------
Merci
Sylfelin
Je l'ai fait en suivant ceci et cela fonctionne.
http://www.sharepointblogs.com/andynoon/archive/2007/09/18/reparenting-a-workflow-to-a-different-list.aspx
****
ci-dessous copie de la page web pour les archives si un jour elle
disparait
******************
Re-parenting a SharePoint Designer workflow to a different list
Before I start there is a good guide to transforming a SharePoint Designer
workflow to a visual studio .net workflow here: Porting SharePoint
Designer Workflows to Visual Studio. This will allow you to package a
workflow up as a feature and deploy and use it in multiple locations in
your farm. However for simple deployments you may want to stick with
SharePoint Designer, if you do - read on!
Within the same site:
So you've got a workflow and now you want to either move it to another
list or attach it to another list at the same time. The list you want to
attach it to is in the same site. You would think there was a way of
associated a workflow with more than one list but in fact there isn't and
to some degree it's understandable. A lot of the actions you define in
the workflow are specific to the library you are working with, even if you
were to abstract your logic away from the list then SharePoint Designer
links actions such as "Current Item" properties to the underlying list.
So, unfortunately it's not as easy as just editing the configuration XML
file:
[workflow name].xoml.wfconfig.xml
and pointing it at the XOML and RULES files for your existing workflow.
Your workflow will almost certainly contain references to the original
library or list, so just pointing the config file at you existing workflow
will have some pretty uncertain outcomes!
The good news is that you can use a lot of what you've already created and
apply it to a new workflow, as per...
Make sure the new list your working with is set up correctly (content
types, columns, approval, check in /out...)
In SharePoint Designer, create a blank workflow with a dummy step defined
Copy the contents of your original XOML file named, [workflow name].xoml
to the new XOML file that was created when you created the new workflow
(use notepad) NOTE: The XOML contains all the variables and activity
definitions for your workflow, but not the logic
Copy the rules [workflow name].xoml.rules file contents to the new rules
file NOTE: The rules file contains the login for if, then...else
comparisons
Compare your config [workflow name].xoml.wfconfig.xml file with the
original config file and make relevant changes (probably just need to
reference the content types created when requesting data from users)
Check through the workflow and change any fields linked back to the
original document library - THIS IS THE MOST LABORIOUS JOB!
UPDATE...ACTUALLY IT'S QUICKER AND EASIER TO OPEN THE XOML AND DO A GLOBAL
SEARCH AND REPLACE LOOKING FOR THE GUID OF THE ORIGINAL LIBRARY AND
REPLACING THAT WITH THE GUID OF YOUR NEW LIBRARY (GET THE GUID FROM THE
URL LINKS ON THE SETTINGS PAGES, THE "AUDIENCE TARGETING SETTING' LINK IS
PARTICULARLY HELPFUL!)
To a different site:
Your workflow is great and now everyone wants a go! You need to deploy
not just within the same site but to another location in your farm
The steps here are similar to the above, with the exception that you will
have to copy all the files that are required to run the original workflow
to the new location. These files are usually just the ASPX pages that are
run when you collect data from a user, you'll need to change the config
file to associate the workflow with the files in the new location. Better
still copy the files to a central location and reference them this
location in both workflow's. That way you only have one set of files to
keep up to date.
After you've done this you can follow the steps above to make the
necessary changes.
Neither of these approaches is really ideal and to be honest there should
be tools to make this process easier, you can kind of see from the
structure here that there is an app waiting to be written for this and if
I have the time maybe I'll put one together. In the meantime please feel
free to comment if you know of a simpler method.
Published Sep 18 2007, 11:40 AM by Andrew Noon
Filed under: MOSS 2007
--
--------------------------
Merci
Sylfelin
Je l'ai fait en suivant ceci et cela fonctionne.
http://www.sharepointblogs.com/andynoon/archive/2007/09/18/reparenting-a-workflow-to-a-different-list.aspx
****
ci-dessous copie de la page web pour les archives si un jour elle
disparait
******************
Re-parenting a SharePoint Designer workflow to a different list
Before I start there is a good guide to transforming a SharePoint Designer
workflow to a visual studio .net workflow here: Porting SharePoint
Designer Workflows to Visual Studio. This will allow you to package a
workflow up as a feature and deploy and use it in multiple locations in
your farm. However for simple deployments you may want to stick with
SharePoint Designer, if you do - read on!
Within the same site:
So you've got a workflow and now you want to either move it to another
list or attach it to another list at the same time. The list you want to
attach it to is in the same site. You would think there was a way of
associated a workflow with more than one list but in fact there isn't and
to some degree it's understandable. A lot of the actions you define in
the workflow are specific to the library you are working with, even if you
were to abstract your logic away from the list then SharePoint Designer
links actions such as "Current Item" properties to the underlying list.
So, unfortunately it's not as easy as just editing the configuration XML
file:
[workflow name].xoml.wfconfig.xml
and pointing it at the XOML and RULES files for your existing workflow.
Your workflow will almost certainly contain references to the original
library or list, so just pointing the config file at you existing workflow
will have some pretty uncertain outcomes!
The good news is that you can use a lot of what you've already created and
apply it to a new workflow, as per...
Make sure the new list your working with is set up correctly (content
types, columns, approval, check in /out...)
In SharePoint Designer, create a blank workflow with a dummy step defined
Copy the contents of your original XOML file named, [workflow name].xoml
to the new XOML file that was created when you created the new workflow
(use notepad) NOTE: The XOML contains all the variables and activity
definitions for your workflow, but not the logic
Copy the rules [workflow name].xoml.rules file contents to the new rules
file NOTE: The rules file contains the login for if, then...else
comparisons
Compare your config [workflow name].xoml.wfconfig.xml file with the
original config file and make relevant changes (probably just need to
reference the content types created when requesting data from users)
Check through the workflow and change any fields linked back to the
original document library - THIS IS THE MOST LABORIOUS JOB!
UPDATE...ACTUALLY IT'S QUICKER AND EASIER TO OPEN THE XOML AND DO A GLOBAL
SEARCH AND REPLACE LOOKING FOR THE GUID OF THE ORIGINAL LIBRARY AND
REPLACING THAT WITH THE GUID OF YOUR NEW LIBRARY (GET THE GUID FROM THE
URL LINKS ON THE SETTINGS PAGES, THE "AUDIENCE TARGETING SETTING' LINK IS
PARTICULARLY HELPFUL!)
To a different site:
Your workflow is great and now everyone wants a go! You need to deploy
not just within the same site but to another location in your farm
The steps here are similar to the above, with the exception that you will
have to copy all the files that are required to run the original workflow
to the new location. These files are usually just the ASPX pages that are
run when you collect data from a user, you'll need to change the config
file to associate the workflow with the files in the new location. Better
still copy the files to a central location and reference them this
location in both workflow's. That way you only have one set of files to
keep up to date.
After you've done this you can follow the steps above to make the
necessary changes.
Neither of these approaches is really ideal and to be honest there should
be tools to make this process easier, you can kind of see from the
structure here that there is an app waiting to be written for this and if
I have the time maybe I'll put one together. In the meantime please feel
free to comment if you know of a simpler method.
Published Sep 18 2007, 11:40 AM by Andrew Noon
Filed under: MOSS 2007
--
--------------------------
Merci
Sylfelin
> Cela fonctionne, parfait, merci pour la communauté.
> Cela fonctionne, parfait, merci pour la communauté.
> Cela fonctionne, parfait, merci pour la communauté.
Cela fonctionne, parfait, merci pour la communauté.
Rien de plus normal.
Sinon pour les personnes qui travaille, comme moi, sur wss à temps partiel
et qui sont à la recherche d'information, j'ai remarqué qu'il est beaucoup
plus facile de trouver des informations si vous formulez vos recherche en
anglais.
Messieurs les francophones vous allez devoir passer à l'anglais.
Bonne soirée à tous et merci à tous les contributeurs et autres MVP pour
leurs blogs avec leurs articles.
--
--------------------------
Merci
Sylfelin
Cela fonctionne, parfait, merci pour la communauté.
Rien de plus normal.
Sinon pour les personnes qui travaille, comme moi, sur wss à temps partiel
et qui sont à la recherche d'information, j'ai remarqué qu'il est beaucoup
plus facile de trouver des informations si vous formulez vos recherche en
anglais.
Messieurs les francophones vous allez devoir passer à l'anglais.
Bonne soirée à tous et merci à tous les contributeurs et autres MVP pour
leurs blogs avec leurs articles.
--
--------------------------
Merci
Sylfelin
Cela fonctionne, parfait, merci pour la communauté.
Rien de plus normal.
Sinon pour les personnes qui travaille, comme moi, sur wss à temps partiel
et qui sont à la recherche d'information, j'ai remarqué qu'il est beaucoup
plus facile de trouver des informations si vous formulez vos recherche en
anglais.
Messieurs les francophones vous allez devoir passer à l'anglais.
Bonne soirée à tous et merci à tous les contributeurs et autres MVP pour
leurs blogs avec leurs articles.
--
--------------------------
Merci
Sylfelin