I used EA to import some source code. However, the name contains name::className. How can I get rid of name? If I highlight name::className it only displays className for editing?
Its an option in EA that you can turn on or off in order to show the namespace.
Check Tool|Options|Diagram and check the option "Disable fully scoped object name"
You can disable 'namespace' at individual diagram level as well. Go to 'diagram' properties-->diagram tab-->uncheck 'show namespace' option.
I know it is dirty but if the imported items need significant massaging, I will rename the .EAP to .MDB and then use sql updates in MS-ACCESS. Once I am done, I rename back to EAP.
Related
We have renamed section in Bitrix as below.
Deals -> Projects, Companies -> Deals, Contacts -> Companies, Leads -> Contacts, However, while we open any of above, still require some renaming.
Top of the page it shows Company where it should be Deals
Products comes with empty.
Please advice.
Thanks
your host name / bitrix/admin/fileman_file_edit.php?lang=en&site=s1&path=%2Fbitrix%2Fcomponents%2Fbitrix%2Fcrm.company.show%2Ftemplates%2F.default%2Flang%2Fen%2Ftemplate.php&full_src=Y you can changes in this file for your tab label name and save it. I am find out it from search option.
You should not rename interface in such way because it confuses users!
It's not just names, they imply a lot of business logic.
Try to explain the reasons why you want to do this (what kind of business problem you are solving) and I will try to help to implement them in the right way.
But if you really want to rename items try to use localization module to translate interface strings (copy En locale and change some strings as you want).
I think it is the best option in your case.
You can find L10n module in admin interface:
How can i localize the drop down option for the search mode? I did some digging and was able to adjust the localization for the search form labels but i'm at loss here.
The CMS Module SearchDialog.ascx call the drop down list here, but i can't see where the values come from.
<cms:CMSDropDownList runat="server" ID="drpSearchMode" CssClass="DropDownField" />
Go to the localization App and create resource strings for
"srch.dialog.AllWords"
"srch.dialog.AnyWord"
"srch.dialog.anywordorsynonyms"
"srch.dialog.ExactPhrase"
Believe those are the 4 you need.
I couldn't find official documentation that helps much with this, though there have been articles in the past on older versions. However, one trick I've used previously is to look in the ~/CMSResources/cms.resx file, find the localized string there, and add a new one with the same key to the Localization module in Kentico. That is, add a new resource string in Kentico with the same key (the naming will be different depending on your version of Kentico).
Here's the docs discussing setting up a multilingual interface: https://docs.kentico.com/display/K9/Setting+up+a+multilingual+user+interface
And here's a screenshot of the resx file:
So in your case I'd create a new resource string within Kentico called "srch.dialog.allwords" as an example and that should overwrite and take priority over whatever is in the .resx file, plus you can manage it via the Kentico admin. There may be a quicker or more reliable way to view the list of default resource strings but in my recent installs of Kentico, the list is hidden from the admin interface.
Alternatively, of course, you could manage the resource strings via various .resx files as in the documentation, but I try to manage as much of these pieces via Kentico as possible for convenience.
I have a basic need to protect the integrity of note text in my system; specifically, once a note has been created, no CSR should be able to edit it (higher levels, maybe). Ideally, it should be immutable once created, but I'll allow the CSR that created it to edit it if that's what's necessary; the big deal is that nobody else should have that access.
The basic role permission that enables this is the Write permission of the Note entity. By setting this to "No Access" but still granting access to Create and Append, users can still write new Notes on any Entity they can "Append To" from a form where the notes exist as a subgrid, but they cannot edit any existing Note.
There are, however, two problems with this. First, I lose the "Add New Note" button in the Ribbon. Not a huge deal but it does force the user to add Notes using the inline editor of the subgrid. The bigger deal is that I lose the Attach File button. CSRs still need to be able to attach files, even if they can't edit notes once created.
Is there a way to do what I need?
If it's only GUI protection you're looking for, you might simply set the field to not editable from on load script.
Can anyone help me with this here codedui? I can't seem to find the option to choose when doing a recording on what properties for the object map to use. like for example,
when I do a recording for a calculator or "Something" and do an action/a click on "button 1" It just directly gets all the properties like, ID, name, classname etc. for that single object.
So, my question would be is there any possible settings when recording that I could tick like just use a couple of the properties not all? (ie. ID)
BTW, I'm using VS2010 ultimate.
Cheers,
Kerwin
UIMap editor that comes with feature pack 2 is the best solution for editing seacrh/filter properties of the control.
I have been working on something similar but haven't come up with a really good solution there are a few options but none of them are particularly user friendly or intuitive. You can hook the UIMap save function and prevent it from recording unwanted properties, note that this can make your tests brittle less properties generally means more failed searches. The UIMap is made by an XML file and you can parse and edit it directly. If you only have a few properties to get rid of you can use the UIMap editor that comes with feature pack 2.
Situation:
A custom "Master Document" content type inherits from Document
The "Master Document" content type has five additional choice fields
There are five custom "Document Template" content types that inherit from the "Master Document" content type
Each of the "Document Template" content types uses a different Word document template (.dot) file
Each of the "Document Template" content types have been added to a document library
Problem:
I click on a document in the library
Document opens up in Word 2003 for me to edit
I make some changes and save
A box pops up called "Web File Properties". The window contains all of my custom metadata properties and the ContentType field. The ContentType field is set correctly to the current content type. The other fields are reset to their default values. This same window can apparently be opened by going to File -> Properties
This window by itself would be fine except for two reasons:
It includes the ContentType column
All of my custom metadata properties are visible but are reset to their default values instead of whatever values were previously selected. This means, every time the user wants to save the document, they have to remember what properties were tagged and set them back.
Question:
Can I disable this Web File Properties box?
If no... can I get the fields that show up to be populated to their correct values?
If no... is there a way to disable my fields from displaying in this window?
If no... is this a SharePoint page that I can modify?
***Edit with some more information***
It looks like this only happens in Office 2003 and looks like it affects Choice fields. If I create the same column as a Lookup field, it seems to work.
Edit again
Looks like if the lookup field is a multi-select field then it will not show up in the Web File Properties box at all (single select lookups still work).
edit 10/14/2009
Link to the KB Article mentioned below by Brenda:
http://support.microsoft.com/kb/971500/
This is more of a workaround rather than an answer but I figured I might as well put it here in case it helps someone else.
It seems as if these issues with the Web File Properties box is specific to Office 2003. The issues I reported above seem to be fixed in Office 2007.
If you want to get it working in 2003 and you have choice/lookup fields in your Document content type, here is the summary:
Single select Choice fields DO NOT work
Multi select Choice fields DO work
Single select Lookup fields DO work
Multi select Lookup fields DO NOT work
FYI - I want to CORRECT my previous post. The fix DID FIX my problem after I deleted my internet cache. Works PERFECT now. Here is the KB you need: KB971500 I can email you the fix if you can't find it. The notes in the document do not describe the problem exactly as I would have, but it was the fix for my case.
bhartson#lbrealty.com
We have the EXACT problem. I've opened a case with Microsoft back in February and they were able to finally duplicate my problem.
I have been kept informed and told that my fix would be available with the JUNE cumulative upates. I just received a specific hotfix from my Microsoft rep and applied it and it still did NOT fix my problem. I am hoping he gave me the wrong one and has the real one to send me.
Thanks for your post. I'm may try some of your suggestions above but I just want Microsoft to fix this. We can't upgrade to Office2007!
Thanks.
man, this was really killing me, I spent an entire day recreating document libraries and all sorts of content-types and variations of my excel template before I figured this was a bug... At least MS has a little hotfix request thing now... they're going to send it to me I guess :\
I didn't test this in excel/office 2003 and really botched a presentation of our little workflow... embarassing... always test with the app & environment people are going to use!!!
thanks for the KB article number