Kate Marsh さんのグループアクティビティ

Disabling all fields in the form using method

hkhan — Tue, 01 Sep 2020 20:45:29 GMT

How can i disable all fields on a form and enable only one using code, without putting all field names in the code except one which is to be disabled.

Aras Fundamentals: Forms and Views

Kate Marsh — Mon, 27 Apr 2020 14:21:00 GMT

This Fundamentals post will explain how Views and Forms can be used in Aras Innovator. The examples will build on the Purchase Order ItemType created in previous Fundamentals posts, specifically Creating an ItemType and Adding Detailed Properties.

A Form is what the user interacts with to author or view data in Aras Innovator. They are used to create, change, or view Items and data. A View is the Relationship between an ItemType and the Form. An ItemType can have multiple Views and Forms, which can be shown depending on how a user is interacting with the Item. These types of Forms are Default (which will show for everything), Add, Edit, View, Print, Complete, and Preview. Admins can change how Users see and interact with Forms, as well as which Forms a User sees and when. This blog will cover the basics of adding a Form and View to an ItemType. Forms are defined (and modified) using the Form Editor, and are then associated to an ItemType on the View Relationship Tab.

The Form Editor

The Form Editor includes standardized controls for designing Forms, and is divided into four main areas:

Properties: A list of all Properties that have been added to the Form. Clicking on an element in the list will highlight the Field in the Form Layout area and update the information in the Field Definition tabs.
Field and Form Definitions: Specific information about each Field and the Form. Each tab’s information and use are explained later in this blog.
Form Layout: A click-and-drag area to design the layout of the Form that the user will see
Field Toolbar: A series of controls that can be added to a Form and can then be associated with a Property. This is also where the xClass Tree Hierarchy for Extended Classification can be added, using the Add New xClass button.

Field and Form Definition Tabs

Field Type Tab

Name: The name of the HTML field element
Field Type: The data type for the Field, this changes the overall look of the Field
Data Source: The Property value that is defined by this Field
Display Length and Display Length Unit: length of the Field and the units to measure

Field Label Tab

Label: The text of the Field’s label
Label Position: Where the label is placed relative to the Field itself
Text Alignment: Aligns label text when positioned above or below the Field
Font Information: Adjusts the font styling for the Field label

Field Physical

Positioning: How the Field is set up in the Form; Absolute X&Y (default and recommended) measures from the top left of the Form, Relative X&Y measures from browser placement, and Static ignores X&Y values and uses only browser placement
X & Y: Coordinates for the Field’s position
Field Order: When the Field is in a group box, specifies the order of the Field
Tab Index: The tab-through order of the Field (if Tab Stop is checked)
Z-Index: The order of overlapping layer – the greater the value, the further to the front an element is
Visible: Displays or hides the Field element
Disabled: Make the Field read-only

Form Properties

Name: Name of the Form
Identity: Who has access to the Form, this is defined in the ItemType’s View tab
Function: Specifies what function (Edit, View, Print, etc.) uses the Form; default is both editing and viewing
Classification: ItemType classification associated with this Form
Description: Details about the Form
Width & Height: Dimensions of the Form in pixels
Style Sheet: Add custom CSS for the Form to use
Category Form: Displays the Form in the Workspace Pane when the user clicks on the TOC Category, the Form name must match the Category value

Form Body

Background Color:
Image: Adds a background image
Repeat: Tiles the background Image
Attachment: Whether scrolling moves the Form or if the Form is fixed
CSS: Add custom CSS for the Form

Field Border: Useful for defining a Group Box or adding a border to a Field

Field CSS: Add custom CSS to the Field

Field Event: Add Methods that are triggered by something happening in the Field

Form Event: Add Methods that are triggered by something happening in the Form

Creating a Form

From the Table of Contents navigate to ItemTypes, search for the Purchase Order ItemType and open it for editing. Open the Views Relationship tab and click the Create Item button. A new row will be added to the grid. The first Form we add should have the Type (Default) and Identity (World), let’s keep those settings for now so the Form is viewable for every User under any circumstance. If we wanted to change when this Form is used or who can see the Form, this is where we would do that. Right click on this and select open to go to the Form Editor.

First, we need to add a name to the Form; click on the Form Properties tab and enter the name as Purchase Order. We want to add the seven custom Purchase Order Properties to the Form: _name, _price, _ponumber, _customer, _phone, _province, and _country. The easiest way to do this is to click on the Unused Properties dropdown menu in the Field Toolbar and select each of the Properties to add them to the Form. Adding the Fields this way will automatically associate the Field with the specific Property as its Data Source and choose the appropriate type for the Field. These settings can be changed in the Field Type tab as needed. If you’re building a Form without first relating it to an ItemType, you can Create Empty Fields from the toolbar and change their settings and properties manually.

Next, we’ll want to tweak a few Field settings and set the Form layout before we can call this Form done. Let’s start with the PO Number.

Disabling Fields

The PO Number will be automatically assigned to the Item when it’s saved, so users shouldn’t be allowed to enter or edit the value of the Field. We may still want to see that information, though, so we can leave it in but disable editing by checking the Disabled box under the Field Physical tab. Any Field Type can be disabled, though disabling something like a Group Box won’t disable its contents.

Grouping Fields

It also makes sense to group the Country and Province Fields together, since they make up the shipping information and one is a Filtered List dependent on the other. Start by adding an Empty Field to the Form using the Field Toolbar (the type doesn’t matter, as there is no empty Group Box button). With this Field selected, navigate to its Field Type tab and select Group Box from the field type dropdown, enter the name as shipping and set the orientation to vertical. Click over to the Field Label tab and delete the content of the Label field. Click on the Field Border tab, enter Shipping Information for the legend, a border width of 1 and a container name of shipping. Next, we’ll update the Country and Province Fields, in the Field Border tab set the container name to shipping, and in the Field Physical tab set the positioning to static and the field order to 1 and 2, respectively. The Form may need to be saved before these changes appear.

Moving Fields

We can clean up the Form’s layout in two ways. The X and Y coordinates of the Field can be manually entered in the Field Physical tab, and the top left corner of the Field will align to those values. If we want to move objects with the mouse, Fields can be click-and-dragged around the Form Layout space. Optionally, Form Layouts can be made neater by enabling the ‘Snap’ option in the Field Toolbar. Choosing a snap value of 5 or 10 will automatically place moved elements on the nearest fifth or tenth pixel in the Form Layout area, respectively.

When everything is aligned, we can click the Save, Unlock, and Close button. We can test out the Form by either creating a new Purchase Order or opening an existing one for editing.

Conclusions and Congratulations

And we’re done! We’ve learned how to create a Form and customize its appearance. Since we built it from the ItemType View tab, it was automatically related to that ItemType. This blog just scratches the surface of everything that Forms and Views can do, so be on the lookout for more Aras Fundamentals post on Forms and Views. Or check out the Forums to ask and find answers to specific questions.

The Mapped Document Elements Enhancement

Kate Marsh — Mon, 14 Sep 2020 15:30:00 GMT

Mapped Document Elements (MDE) are a core feature added to the existing Technical Document Framework (TDF) application, released in Aras Innovator Version 12 Service Pack 5 for all users. This enhancement allows for the association of Document Elements in a TDF-enabled document to a Property of a referenced Item. A Document Element to Item Property association means that the properties of the Item in the Tech Doc will update as the Item’s property is updated. Additionally, the Element can be flagged with ‘write’ permissions to allow for editing and saving the Property value directly from the Tech Doc.

MDE is a useful feature for ensuring a Tech Doc’s references to an Item stay updated as the Item’s properties are changed. One application of this feature is documenting the most recently calculated cost of Parts in an assembly. This blog post will cover enabling MDEs for Part Items and mapping a Part Item’s name property to a Technical Document.

Enabling Mapped Document Elements in TDF

By default, the new Mapped Document Elements are not included in the Standard schema, to prevent any unexpected behavior with existing ItemInfo Elements in Tech Docs. We’ll need to create a new schema to utilize the enhancement.

Go to Technical Documentation > Document Types in the TOC
Right click and select Create New Document Type
Fill in the name field with ‘MDE Enabled’
In the content section, copy and paste this code:
gist.github.com/.../24420dfa39e6af880ce0a17f456c56f1
In the Stylesheet tab, click Add New Document Style
1. Enter the name ‘MDE Enabled Stylesheet’
2. Right click and select Stylesheet > Open
3. In the style section, copy and paste this code:
  gist.github.com/.../3d5e5e5eaecbd8c302874fea7fb1ea2a
Click on the Validate button, the schema should be valid
Click Done to save

Adding an MDE to the Document

Now that the schema is made, we can start to build our Tech Doc. First, we’ll want to create a Tech Doc that uses our new Schema:

Go to Technical Documentation > Technical Documents in the TOC
Right click and select Create New Technical Document
Fill out the form’s required information:
1. Document Number – ‘MDE-0001’
2. Name – ‘MDE-Test’
3. Schema – MDE Enabled
Save (but don’t close) the new Tech Doc
Click on the Tech Doc Editor tab that was added to the left side column

From the Editor tab, we can start adding elements to our Tech Doc. Adding a Mapped Document Element is like adding any other Element to a Tech Doc, with some additional steps for selecting the specific Part. Just follow the steps below:

Right click on the root element and select Insert > Item Info > Add Item. In the dialog, search for and select the desired Item, then click OK
Right click the ItemInfo entry in the tree and select Insert > PartStatement > Add Item. In the dialog, search for and select the desired Item, then click OK
Right click the PartStatement entry and select Insert > Any Property
Right click on the AnyProperty entry and select Edit Attributes to open a dialog
1. In the property field, enter ‘name’
2. Select ‘write’ for the mode
3. Click apply
Save (but don't close) the Tech Doc

While the Tech Doc is claimed and in edit mode, you can double-click on the Property in the editor pane to open a pop-out field editor. When selected, an MDE with write permissions will have a gray dashed border, while a read-only MDE will have a solid red border. Changes made in that field can be added or discarded by clicking on the check or x boxes, respectively. Once a change is made, the element in the tree and its parent element will be marked as changed with a pencil icon; clicking on that icon will open a dialog prompt to revert the changes. To save any changes made to an Item, just click Save or Done. On a save, any changes to Properties will be validated by the system.

Additionally, if changes have been made outside of the Tech Doc, the property in the editor will be highlighted with a red dashed border. The right click menu on the PartStatement tree element will now contain a Version menu, which gives you option to update the data to reflect the latest version, ignore the current version, or ignore this and all new versions and changes.

We’re excited to share this enhancement to the Tech Doc Framework; this core feature will enable other new features in future Requirements Engineering and Technical Documentation application releases. To take advantage of the range of options available in Technical Documents, check out our previous blogs that cover other ways to customize your Tech Docs, such as custom content generators, adding links to Documents, and creating templates. We also have a GitHub repo with a number of custom Technical Document examples to use as ideas for your own Tech Docs.

Defining a workflow process and map vs process plan

Duncanwilliamgibbons — Tue, 28 Jul 2020 17:44:32 GMT

If my understanding is correct. a lifecycle is the states an item (be it a part, equipment or document) goes through.

The manufacturing process plan is the plan (list of operations and steps) required to realize a part or product.

Then what is the workflow map, process, activity, assignment and task? And can a workflow process not be the same as a manufacturing process plan?

Is there possibly a document that clearly defines these, their relation to one another and to which items they relate to (part, product, document etc.)

Thanks

how to enable a disabled date picker on the form

Plugg — Fri, 14 Aug 2020 17:43:50 GMT

I have a date that is disabled on the the form. I run a javascript method to enable the date. the mehtod is set to run on the form event of 'onFormPopulate'. I can enable the text field portion of the date, but the datepicker(calendar pop-up), will not enable. I cannot get the calendar to allow me to select a date. Is there a way to enable the calendar?

getFieldByName("_actual_plan_bill").getElementsByTagName("input")[0].disabled = false;

Enhancements to the Technical Document Framework

Kate Marsh — Thu, 30 Jul 2020 20:00:00 GMT

The Aras Technical Documentation application has been a powerful tool for creating technical publications with multiple data sources quickly while reducing the chance for errors related to copying data. The Technical Document Framework (TDF) is available to all Aras users, and can be downloaded and installed using the Aras Update Utility. The TDF enhancement we’ll cover today (introduced in 12.0 SP4) enables users to create and use existing Tech Doc-enabled content as a template in another Tech Doc. The template Document is added to the target Document as a full copy. Using this feature, a common element in your Tech Docs can be made into a template that can be reused, and multiple templates can be used to create modular documents. In this example, we’ll go over the steps required to create a custom Tech Doc template and then insert it into another Technical Document Item.

Creating the Template

We’ll start by creating the template, we can create our Tech Doc template just as we would any other Tech Doc:

Go to Technical Documentation > Technical Documents in the TOC
Right click and select Create New Technical Document
Fill out the form’s required information:
1. Document Number – ‘Tmpl-01’
2. Name – ‘TDF Template’
3. Schema – Standard
Save (but don’t close) the new Tech Doc

Once saved, the tab for the Tech Doc Editor should be added to the brown column on the left, click on that to open the editor.

For now, let’s keep this template and explanation simple and just add a title and a table.

In the Document Tree column on the left side, right click on the area labeled TDF Template (the root element)
Click Insert > Title then type to fill the yellow region that is added to the editor to the right
Right click on the Title element in the document tree and select Add > Table
1. In the resulting dialog, set both to the row and column attributes to 3 then click OK
2. Confirm that the table is added to the editor area and to the left column as a collapsible tree with three child rows, each with three child entries
Click on the first column and row in the table and start typing in the first header box, then click to the next column or tab through to fill out the table
Click Save and Close and to finish the template

Adding the Template to a Document

Next, we’ll make a new Technical Document. As before:

In the TOC, go to Technical Documentation > Technical Documents
Right click and select Create New Technical Document
In the form, enter in the required fields:
1. Document Number – ‘Doc-01’
2. Name – ‘TDF Document with Template’
3. Schema – Standard
Save the Tech Doc, then click on the editor tab
Add two section elements by right clicking on the root element and selecting Insert > Section. The sections will each be added with a child title element
Fill out the first section:
1. Type in a title for the first section
2. Right click the title element either in the document tree or in the editor and select Add > Text twice
3. Enter some filler text in both text fields using the editor
Add a title to the second section, then right click on the section element in the document tree and click Add > From Template
In the item selection dialog, search for the template document, select it, and click OK
Save and Close the Tech Doc

There are a few things to note. For a template to be added to a Tech Doc, both must use the same the schema. Additionally, adding elements "From Template" differs from adding "External Content". With external content, the elements of the source and target documents are identical and cannot be changed independently. When adding from a template, the elements are inserted as a copy, so the source and target documents can be modified without affecting the other

Here’s what the final result should look like:

Closing Remarks

The Technical Documentation Template enhancement works with previous methods of customizing your Tech Docs, allowing us to create new Documents faster than ever. If you want to continue taking full advantage of the power of Tech Docs, be sure to check out some of our previous blogs that go into detail about custom content generators and adding links to Documents. Additionally, we have compiled a collection of custom Technical Document examples on this Github repo for implementation ideas.

Aras Fundamentals: Customizing Relationships with the RelationshipType

Kate Marsh — Mon, 15 Jun 2020 15:33:00 GMT

When a Relationship is defined on an ItemType, two new Items are created: a Relationship ItemType and a RelationshipType. In a previous blog post, we went over how to create a new Relationship for an ItemType and some basic aspects of configuring the Relationship, most of which took place on the Relationship ItemType. This Aras Fundamentals blog will expand our ability to customize a Relationship by adjusting settings on the RelationshipType Item. We’ll be working with the Purchase Order ItemType from previous Fundamentals posts, too.

First, we’ll set a minimum number of Part relationships required for a new Purchase Order to be saved. Then we’ll discuss how to hide the Relationship Tab in the Item Editor, and why we’d want to do that. Finally, we’ll customize what a Relationship Tab displays based on who is using the Relationship View.

Minimum and Maximum Occurrences

Let’s open up the Purchase Order Part RelationshipType for editing (not the ItemType!), which can be found under Administration > RelationshipTypes > Search RelationshipTypes. When a new Purchase Order is created, we want at least one Part to be attached to it before it can be saved. To ensure that this happens, we’ll set the Minimum Occurrences (in the Related group box) to 1. Now, save and unlock the Item and we’re done! We can test this out by creating a new Purchase Order and trying to save the Item without adding a related Part; an error dialog will be shown to us indicating what the problem is.

This method also works if we want to set a maximum number of entries of a RelationshipType, just enter the maximum value in the Max Occurs field. Both occurrence checks can be used simultaneously, just be sure that the minimum is less than the maximum. Additionally, if we wanted to remove any occurrence checks, we would leave the field blank (rather than enter in a value of 0).

Hiding the Relationship Tab

Next, let’s go over the “Hide in All” option for the RelationshipType (In the Source group). Checking this option will hide the tab for this ItemType on the Relationship Grid of the parent Item. This is useful for any Relationships that are set and used behind the scenes, but that end users don't need to see.

Customizing the Relationship View

Sometimes, when we have a Relationship, the standard grid layout isn’t the best way to show the information for that Relationship. Or possibly we want to have different Views depending on what User is looking at the parent Item. Building a custom view from the ground up is beyond the scope of this blog, so we’ll use two existing RelationshipTypes as examples: Project Tree on the Project ItemType and Part Multilevel BOM on the Part ItemType. Let’s take a look at the Project Tree RelationshipType first.

The Project Tree’s Relationship View is set for the World Identity, so all users will see the Relationship View. The Start Page value is set to an HTML file so when the Project Plan Tab is opened, a custom HTML page is loaded instead of the standard relationship grid, as shown below.

The Relationship View for Part Multilevel BOM has the Start Page pointing to the Tree Grid View main page. In order for this page to display the Part Item’s data correctly, we also need to pass in Parameters such as the ID of the Tree Grid View and a start condition with the source ID of the Part Item. When we open the BOM Structure Tab on a Part that’s an Assembly, we can see the entire bill of materials in an expandable list.

Conclusions and Congratulations

Today, we dug deeper into the ways we can customize our Relationships in Aras Innovator, with a focus on the RelationshipType. We started simple, with setting minimum and maximum limits on the number of related Items. Then we discussed hiding a Relationship Tab, and when it would be useful to do so. Finally, we showed two examples of changing what’s shown in the Relationship Tab using the Relationship View. Thanks for reading this Aras Fundamentals blog! There are more in the series that help explain different concepts and ItemTypes within Aras Innovator. Or visit the Forums to ask and find answers to specific questions.

How to hide Design Quality Docuement and Process Quality Document option in selection dialog?

Joseph An — Thu, 05 Mar 2020 02:03:52 GMT

Hi Expert,

I tried to hide 'Design Quality Document' and 'Process Quality Document' option from the Dialog below that is populated from Corrective Action Plan.

So that, a user can see only on ECO and Document. Can we also show DCO too to add DCO?

Thank you so much for your help in advance.

Joseph

Calling server method from another server method

Suhas — Mon, 09 Mar 2020 14:38:06 GMT

Hello All,

From one server method (Method A ), I'm calling another server method (Method B) .

From (Method B) returning inn.newError("Error");

And in calling method (Method A) checking result has error but it is not working. Error message is showing directly on UI.

Item X = inn.applyMethod("Method_B","");

if(X.isError())

{

//execute xlogic

}

else

{

//execute y logic

}

But if case is not executing & error message directly displaying on UI.

Regards,

Suhas

(Mostly) white screen after login.

gking — Thu, 05 Mar 2020 16:28:02 GMT

Downloaded and installed 12 without any issues. Got logged in, and I only have the very top bar across my screen. All of the screenshots I see have the File / Edit / View etc. bar across the top. Am I missing something? I've never actually used Aras before. I set up the sample database and pointed Aras at it without change. I can get the 'quick access', for lack of a better term, bar to open and can navigate through those categories but it just seems like something is missing overall.

Is there a initial configuration guide of any sort?

Aras Fundamentals: Adding Relationships to ItemTypes

Kate Marsh — Wed, 19 Feb 2020 14:45:00 GMT

In this Fundamentals article, we’ll go over how to add a Relationship to custom or default ItemTypes in Aras Innovator. In a previous Aras Fundamentals blog post, we created an ItemType called Purchase Order. And today we’ll be expanding on that ItemType by adding two new Relationships to it. For our Purchase Orders, we want to be able to add a list of Parts associated with the Purchase Order and add comments to the Purchase Order along the way. The first use case requires adding a Relationship to an ItemType, and in the second case we will add a Null Relationship.

What does a Relationship do and why would we want to relate one Item to another, anyways? A Relationship is an Item that connects two Items. Because it’s separated from the source and related Items, it has its own properties, rules and actions – all of which can be customized independently. An Item could link to the most recent version of the related Item or the related Item’s version at the time when the Relationship was made. The specifics of customizing a Relationship’s functionality are beyond the scope of this article, so for now we’ll focus on creating basic Relationships.

Adding a Relationship

Let’s start by adding a Part List to the Purchase Order. The Purchase Order is going to be used to keep track of the Parts requested by one of our customers, so we need some way to store which Parts have been requested. The easiest way to do this is to add a Relationship pointing to Parts by following the steps below:

In the ItemType search grid, search for the Name of the Purchase Order.
Open the Purchase Order ItemType and click ‘Edit’.
Navigate to the RelationshipTypes tab (next to the Properties tab).
Click on the ‘Select Item’ button to define a new RelationshipType. In the search dialog, search for and select the ‘Part’ ItemType by its name.
Fill out the table row for the new RelationshipType.
Start by specifying the tab order, we’ll put 10 – though this only matters if we have more than one Relationship.
In the Name column, enter ‘Purchase Order Part’.
- A typical naming convention for RelationshipTypes is to use the source and related ItemTypes’ names.
Enter 'Part List' in the Tab Label field.
- This will be the name of the tab that the user sees when editing the source item.
Save and Unclaim the Purchase Order ItemType by clicking on ‘Done’.

For each RelationshipType that is created, a Relationship ItemType of the same name will be automatically made. We can add properties and behavior to this ItemType to change the characteristics of the Relationship, as needed. For this Relationship, we don’t need to add or change anything, so let’s continue onwards.

Adding a Null Relationship

Now let’s look at adding a Null Relationship to our Purchase Order ItemType. In a Null Relationship, the RelationshipType has a source ItemType, but no related ItemType. This RelationshipType structure is useful when we need to track items that pertain only to the source item and won’t be reused. For example, we want to add a way to attach comments to our Purchase Orders. The steps to create a new Null Relationship are:

While editing the ItemType, navigate to the RelationshipType tab.
Click on the ‘Add Row’ button to get a new blank row. Note that the far-left column has the ‘Null Relationship’ icon.
Fill out the table row.
Start by specifying the tab order as 20.
- This will make the Comments tab come after the Part List tab.
Enter ‘Purchase Order Comments’ as the name for the RelationshipType.
- A good naming convention is to use the source ItemType’s name and a descriptive name of the new Relationship.
Enter the Tab Label, we’ll set this to ‘Comments’.
The name column stays blank for a Null Relationship.
Save and Unclaim the ItemType by clicking ‘Done’.

We want this Relationship to record comments, so we need to add a property to the Relationship to hold that information. Here are the steps to add a comments property to the ‘Purchase Order Comments’ Relationship ItemType:

In the ItemType search grid, search for ‘Purchase Order Comments’, which was just created when we saved the parent ItemType.
Open the Relationship ItemType and click on the ‘Edit’ button.
Optionally, we can add singular and plural labels to make the table title clearer.
In the Properties tab, click the ‘Add Row’ button.
Name the property ‘_comment’.
- The underscore isn’t necessary, but it’s an easy way to distinguish system-made properties from ones we’ve added.
Change the Label to something more readable, like ‘Comment’. This will be the table header in the Relationship’s tab.
Select Text for the Data Type of the property.
- The comment will be sequence of text without a set length, so the best option here is Text. That way, users can write as much as they need to without being constrained by a character limit.
Make the property visible to the user, by ensuring the boxes under ‘Hidden’ and ‘Hidden2’ are unchecked.
Optionally, set the default Width of the column to a value like 200 so more of the comment can be read in the table.
Save and Unclaim the ItemType by clicking ‘Done’.

Default Structure View

Let’s test out our new RelationshipType by opening a Purchase Order for edit. And … hm, we can’t see the Relationship tabs.

Oh, of course, we forgot to enable the view for the Purchase Order ItemType. That’s an easy fix; we just need to enable the source ItemType to show Relationship tabs when an Item is opened. To do this, we’ll open the Purchase Order ItemType for editing, click on the Default Structure View drop down menu and select ‘Tabs On’. We can then save the changes. Here’s a list of the Structure View options and what they mean:

‘Tabs On’ will display all relationship tabs if there are any associated with the ItemType.
‘Tabs Off’ is the Aras Innovator default and hides the Relationship tabs from the accordion section of the Item.
‘Tabs Min’ adds the relationship tabs to the accordion section but defaults it to closed.
‘Tabs Max’ is currently the same as ‘Tabs On’ but may change functionality in the future.

Now that we can see the Relationships for this ItemType, we can test the new RelationshipTypes by adding them to a Purchase Order Item.

Open a Purchase Order Item for editing.
Add a Part Relationship Item by clicking on the ‘Parts List’ tab.
- I have a premade Part to use, so we’ll click the ‘Select Items’ button and search for the Part, highlight it by clicking on it, and hit ‘OK’ to add the Relationship.
- If you're following along and don't have a premade Part, you can click the 'Create Item' button to add a new Part on the fly.
Add a Null Relationship Item by clicking on the ‘Comments’ tab.
- Click on ‘Add Row’ and fill out the values with our comment.
We’re done adding Relationships to this Item, so we can Save and Unclaim the Purchase Order by clicking 'Done'.

In Conclusion

That’s all we need to do to add Relationships to ItemTypes. We also learned when to use standard Relationships versus Null Relationships. The series of Aras Fundamentals blog posts should help with mastering essential techniques for developing in the Aras Innovator system.

Kate Marsh さんの グループ アクティビティ

Disabling all fields in the form using method

Aras Fundamentals: Forms and Views

The Form Editor

Field and Form Definition Tabs

Creating a Form

Disabling Fields

Grouping Fields

Moving Fields

Conclusions and Congratulations

The Mapped Document Elements Enhancement

Enabling Mapped Document Elements in TDF

Adding an MDE to the Document

Defining a workflow process and map vs process plan

how to enable a disabled date picker on the form

Enhancements to the Technical Document Framework

Creating the Template

Adding the Template to a Document

Closing Remarks

Aras Fundamentals: Customizing Relationships with the RelationshipType

Minimum and Maximum Occurrences

Hiding the Relationship Tab

Customizing the Relationship View

Conclusions and Congratulations

How to hide Design Quality Docuement and Process Quality Document option in selection dialog?

Calling server method from another server method

(Mostly) white screen after login.

Aras Fundamentals: Adding Relationships to ItemTypes

Adding a Relationship

Adding a Null Relationship

Default Structure View

In Conclusion

Kate Marsh さんのグループアクティビティ