Map platform-how to remove the document sequence book and automatically add it when opening it?

The project has the following requirements:

Hide the sequence time book. When you double-click the menu to open the document, it is automatically added.

Solution 1:

1. system maintenance-menu management-new metric entry

2. Remove the view after commandstring and change it to zhibiaoluruxinz (indicating to load the document when you click the tree menu, instead of loading the sequence book)

3. Open the config \ config_hf \ module \ SCM \ Bill \ billmeta. xml file.

Add the following code under the billmetauioptcollection node:

<Billmetauiopt key = "new2" caption = "added" icon = "addnew" Shortcuts = "Alt + N" objectcondition = "tabletype () = & quot; Bill & quot; "precondition =" readonly () "suboptkeys =" newbill; showbill; editbill "suboptdataidxes =" 0; 0; 0 "/>

-- Precondition = "readonly ()" indicates that the data is visible only when it is not edited.

4. Modify the XML file corresponding to the indicator input ticket and add entryuioptkey = "new2" to the most defined form"

<Billemediable key = "zhibiaoluruxinz" caption = "added" tabletype = "bill" id = "79654" version = ". 519 "tablecount =" 2 "metasubhookkey =" "m_lgridcount =" 1 "withoutfilter =" false "btotal =" false "suioptkey =" New; Edit; save; |; newprint; newprintdefault; newprintselect; |; newpreprint; newpreprintdefault; newpreprintselect; |; deleterow; firstbill; prebill; nextbill; lastbill; sendlink "printtemplate = ""Entryuioptkey = "new2">

5. Close the middle layer and re-open the document to see the effect.

Solution 2:

1. Step 1 of solution 1

2. Step 1 of solution 1

3. Modify the XML file corresponding to the indicator input ticket and add entryuioptkey = "newviewbill" to the most defined form"

<Billemediable key = "zhibiaoluru2" caption = "indicator input 2" tabletype = "bill" id = "79657" version = ". 519 "tablecount =" 2 "metasubhookkey =" "m_lgridcount =" 1 "withoutfilter =" false "btotal =" false "suioptkey =" New; Edit; save; |; newprint; newprintdefault; newprintselect; |; newpreprint; newpreprintdefault; newpreprintselect; |; deleterow; firstbill; prebill; nextbill; lastbill; sendlink "printtemplate =" "Scheme =" newviewbill ">

4. Close the middle layer and re-open the document to see the effect.

Differences between solution 1 and solution 2:

Solution 1 is to customize the interface sub-operations, and solution 2 is to call the system sub-operations.

Reference:

Entryuioptkey, closeuioptkey Attribute description

Generally, you can open a form by clicking the menu on the left and then performing an operation to open the form. For example, you can run the viewreport interface operation in a report and check the page to perform the viewhook interface operation, the dictionary executes the opendictionary interface operation, the unordered notebook document performs the newviewbill operation, and the other operations perform the viewbill operation. If we have special operations when opening a form object, we need to bypass these default operations or execute some formulas, then we can define the Open entry operation for the form object, there are two hidden attributes in the form object: entryuioptkey and closeuioptkey. One is to open the document entry operation and the other is to close the document execution, for example, <billemediable key = "costout" caption = "outbound cost calculation" tabletype = "multibill" id = "79518" version = ". 519 "tablecount =" 1 "metasubhookkey =" "m_lgridcount =" 1 "withoutfilter =" false "incluablekey =" "DSN =" btotal = "false" suioptkey = "autofit; uiclose "printtemplate =" "entryuioptkey =" vi Ewmultibill "> the viewmultibill pointed to by entryuioptkey is a custom interface operation. XML is defined in this way <billmetauiopt key = "viewmultibill" caption = "viewmultibill" suboptkeys = "doevaluateformula (addvariable (...)); Doevaluateformula (settablefilter (...)); Loadobject; showbill "suboptdataidxes =" 0; 0; 0; 0; 0 "/>. In this case, I have defined an operation to open the Entity form, and I am working on loadobject; before showbill (intermediate layer fetch-> display form data), I made doevaluateformula (addvariable (...)); Doevaluateformula (settablefilter (...)) One of these two tasks is to add a variable, and the other is to set the filter condition settablefilter for the form, so that I can do something we expected before displaying the document. You can define your own special operations in the entryuioptkey attribute so that the form can be opened according to your own intent. The same is true for closeuioptkey. There are not many interface operations executed when the form is closed.

The entryuioptkey and closeuioptkey attributes are widely used in our standardized products. There are also some complicated interfaces, because we need to do some complicated things before displaying a form, for example, in the multibill_login.xml file in the configuration login window, the portal is defined as <billable key = "login" caption = "login" tabletype = "multibill" id = "79095 "... Suioptkey = "" printtemplate = "" watermark = "_ forminitialize" closeuioptkey = "_ formunload">, the interface operations _ forminitialize and _ formunload pointed to by the lifecycle and closeuioptkey attributes in this region, these two interfaces are operated on billmeta. XML is defined

<Billmetauiopt key = "_ forminitialize" runasexp = "_ forminitialize ()" suboptdataidxes = "0" needrowcheck = "false"/>

<Billmetauiopt key = "_ formunload" runasexp = "_ formunload ()" suboptdataidxes = "0" needrowcheck = "false"/>, which is further explained in the previous section, the runasexp attribute of the sub-operation is used here, which means that a series of sub-operations do not need to be defined later, but execute the _ forminitialize () macro formula, this formula can be written in the formula macro and then defined in the macro as needed. In this way, the macro can be used in multiple places, and the configuration structure is clearer and concise. We can simply look at this macro definition.

<Billmetaexpformulacollection>

<Billmetaexpformula key = "_ forminitialize" Para = "" formula = "showbill (true, true, false, false, true) + setformsizebypixel (366,546)"/>

<Billmetaexpformula key = "_ formunload" Para = "" formula = "addvariable ({login}, false) + uiclose ()"/>

...

</Billmetaexpformulacollection>

If you are interested, you can take a look at the configuration of the multibill_login.xml file and have a deep understanding of the attributes of the two form objects entryuioptkey and closeuioptkey, as well as the macro definition in the document.