I have updated a template of a Work Item in TFS 2015 called User Story. I simply created a rule on a field to set a default value.
To default the field I did the following :
On visual Studio, on the Main Menu, click on Tools / Process Editor / Work Item Types / Open WIT from server.
Browse to the Work Item (User Story in this exemple) Then click OK.
Double click on the field to edit. On the Rules tab. Add a new rule : DEFAULT. From: Value and Value: My Text here.
I can see the change on the user story when I use Visual Studio but not on the Web Portal.
Is there anything that I need to do for the web portal to get get this change?
Could that be a bug ?
Any idea ?
Thanks
I've tested in my TFS 2015.4, and got correct behavior.
Here are my steps for your reference:
Add a new field and make it available on work item form.
Add a DEFAUL rule, the XML looks like:
<FieldDefinition name="test" refname="test.test" type="String">
<DEFAULT from="value" value="mytext" />
</FieldDefinition>
Check this custom field in VS:
Check this custom field on web portal:
Related
In Odoo studio, I "played" around in the widget where there is a selection of data type such as "float".
I mistakenly changed the type from "float" to something else.
Which now I cannot access into Odoo Studio to changed back the setting
I would like to know how to resolve this error
Thanks a lot!
Odoo 14.0+e (Enterprise Edition)
Error as follows
Traceback:
TypeError: Cannot read properties of undefined (reading 'digits')
at Class._render (https://mycompany.odoo.com/stock/static/src/js/forecast_widget.js:34:124)
at https://mycompany.odoo.com/web/static/src/js/fields/abstract_field.js:209:25
To change it back you can open the view which you modified in studio for example if you modified sale order form, open any sale order in form view and enable developer mode and then from debug icon select Edit view: Form, the form view will be shown go to inherited views tab and you will find many views but you will find view with name start with Odoo Studio click on it and then the the inherited view will be opened and from Architecture tab you will see the xml code so you will look into it and comment the widget change using <!-- --> or delete it.
You can check this YouTube Video
I'm new using SharePoint. I am having trouble with find the code or workflow structure of a list or a library. In the left menu i can see the "Workflows" button but all workflows are not there.
There is a workflow section In the "List and libraries" view showing the running workflows in these list, but when i click on one of them it just move me to its settings in the browser and no to the structure or code that is what i'm looking for.
Is there a way to find the code or structure of my running workflows?
PD: I am working in place of the previous developer who build the entire site, however, he didn't show me anything about.
Thanks.
If these are workflows created using SharePoint Designer then:
Open SharePoint Designer
Open the site
Click on Lists and Libraries
Click on the list name
There will be a heading titled "Workflows"
Click on the workflow you are wanting to look at
Click "Edit Workflow" to view it
Go From there
If you are wanting to see the status of a workflow in regards to the item:
Go to the list
I recommend creating a personal view (so only you see it)
You can select the fields you are interested in and each workflow should have a column in the list associated with it. Include the column in your view
Go to your new view and you can click on the link to view the current status of the workflow
Go to All Files > Workflows Folder. Then select the workflow you want to work with. Right Click on the "xoml" file then select "Open With" > "SharePoint Designer (open as workflow)"
Once it's opened, published it again. Then it will show up again in the Workflow tab.
The workflow was a visual studio sequential workflow deployed in the site as a feature. It was not a SharePoint Designer one. Thanks
The manager was some specific fields added to the standard TFS web parts.. I could just make a Sharepoint List but then it would not haev a relation to the TFS bug/Task list..
So is there a way to do this ?
Open Team Explorer for that project.
Menu -> Tools -> Process Editor -> Work Items Types -> Open WIT from Server
From here, you can add additional fields and publish it back out.
Here is an article that will walk you through something similar to what you are trying to accomplish:
Customization of TFS process template – adding field to a Work Item Definition
I'm trying to work out how to get sharepoint 2010 to display the quicklaunch on a web part page, the default.master trick I used in 2007 doesn't appear to work any more.
In my 2007 install, I simply edited the default.master and moved the quicklaunch code outside of the PlaceHolderLeftNavBar element but this doesn't have any effect in SP2010.
Thanks
A simple way to eneble Quick Launch Menu on WebPartPages is remove tags UIVersionedContentUIVersionedContent and PlaceHolderLeftNavBar using SharePoint Designer 2010.
See this article: http://denmartins.wordpress.com/2011/05/07/exibir-menu-quicklaunch-em-webpartpages/
If you really want to place another copy of the quicklaunch on a web part here is the steps
Using Sharepoint Designer 2010 go to your site and navigate to Master Pages -> v4.master
Click edit file copy everything in the <div class="ms-quickLaunch"> that should copy everything you need for the quicklaunch to run. For best result use the code view and hover over the quicklaunch and you should see the div, click on it and copy (Ctrl + C)
Now you can paste that on another web part page and it should work, I tried it by creating a new test page and it worked
You need to make changes in v4.master (in masterpage library), not in default.master.
For details on SharePoint 2010 master pages, please, follow this link:
http://sharepoint-sandbox.com/index.php?/Tips-and-Tricks/Customization/tip-80-sharepoint-2010-new-masterpages.html
Your masterpage trick on my SharePoint Foundation 2010 environment works fine.
Anyway, I don't think, that moving any standard code from placeholder is a good idea. If you want change position of quicklaunch menu, you should move the leftnavbar placeholder itself, including all the contents.
Placeholders are generally used to allow some pages, for example application pages, replace placeholder contents. So, if you hide the placeholder, and move it's contents out, these changes will be lost, and the standard menu will be shown. (and if you do not hide the placeholder, you can get two menus on one page :) )
Hope it helps!
I want to add some extensions to an existing Siebel application, but the objects which I need to change remain (partially) read only, despite I have locked the respective parent projects.
E.g.
Add a Menu item to the application main menu. => I can edit existing items, but I cannot add new items (Tool's menu "New record" is disabled.)
Add a custom applet to view "Sales Home Page View". It's read only (Warning displayed by Tools when I click "Edit web layout").
Any ideas, why?
Seems to be a bug in Siebel Tools. After a restart of Tools I was able to perform the desired changes.