You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+55-15Lines changed: 55 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,26 +2,27 @@
2
2
3
3
This project demonstrates how to customize form field appearance with custom CSS.
4
4
5
-
## Project Details
6
-
7
-
See [TESTSTATUS file](./TESTSTATUS.md) for latest testing information.
8
-
9
-
#### Built Using:
10
-
Aras 11.0 SP7
5
+
## How It Works
11
6
12
-
#### Versions Tested:
13
-
Aras 11.0 SP9 (open release), Aras 11.0 SP7, Aras 11.0 SP5 (open release)
7
+
This project contains two parts - a code tree overlay and an import package. The code tree overlay adds a custom CSS file and several SVG files to the `Innovator\Client\customer` folder. (It is always recommended to store any custom or third party files in the customer folder.)
14
8
15
-
#### Browsers Tested:
16
-
Internet Explorer 11, Firefox 38 ESR, Chrome
9
+
The import package updates the Part form properties to use the custom CSS file added by the code tree overlay. It also adds a Form Event method to override some of the default CSS classes.
17
10
18
-
> Though built and tested using Aras 11.0 SP7, this project should function in older releases of Aras 11.0.
11
+
## History
19
12
20
-
## How It Works
13
+
Release | Notes
14
+
--------|--------
15
+
[v1.2](https://github.com/ArasLabs/custom-form-css/releases/tag/v1.2) | Custom JavaScript function definitions migrated from Field script tags to the labs_StyleForm Form Event.
16
+
[v1.1](https://github.com/ArasLabs/custom-form-css/releases/tag/v1.1) | Code refactored to separate content and presentation.
This project contains two parts - a code tree overlay and an import package. The code tree overlay adds a custom CSS file and several SVG files to the `Innovator\Client\customer` folder. (It is always recommended to store any custom or third party files in the customer folder)
19
+
#### Supported Aras Versions
23
20
24
-
The import package updates the Part form properties to use the custom CSS file added by the code tree overlay. It also adds a Form Event method to override some of the default CSS classes.
@@ -49,6 +50,9 @@ The import package updates the Part form properties to use the custom CSS file a
49
50
* Optional: Enter a description in the Description field.
50
51
8. Enter the path to your local `..\CustomFormCSS\Import\imports.mf` file in the Manifest File field.
51
52
9. Select **CustomFormCSS** in the Available for Import field.
53
+
10. Optional: Select the **com.aras.innovator.solution.PLM** package from the Available for Import field.
54
+
* This adds the labs_StyleForm method to the Part form and updates a few fields. Check out the import package to see which fields are updated.
55
+
* If you don't import the PLM package, you'll need to manually update the form you want to style.
52
56
10. Select Type = **Merge** and Mode = **Thorough Mode**.
53
57
11. Click **Import** in the top left corner.
54
58
12. Close the Aras Package Import tool.
@@ -57,11 +61,47 @@ You are now ready to login to Aras and check out the customized Part form.
57
61
58
62
## Usage
59
63
64
+
### Viewing the Styled Form
65
+
66
+

67
+
60
68
1. Log in to Aras as admin.
61
69
2. Click **Design > Parts** in the table of contents (TOC).
62
70
3. Open an existing Part, or create a new Part to view the customized Part form design. It should look something like this:
63
71
64
-

72
+
### Styling Other Forms
73
+
74
+
Once you have styles defined for one form, you can apply them to other forms as well. These steps demonstrate how to apply the custom styles in this project to the default Document form in Aras.
75
+
76
+

77
+
*The default Document form, without custom styles.*
78
+
79
+
1. Log in to Aras as admin.
80
+
2. Click **Administration > Forms** in the TOC.
81
+
3. Search for the Document form, then open and lock it.
82
+
4. Add the labs_StyleForm method as an **onLoad** form event.
83
+
5. In the **Form Body** tab, enter the following CSS in the CSS field:
84
+
85
+
```(css)
86
+
@import url("../styles/default.css");
87
+
@import url("../customer/myStyles.css");
88
+
```
89
+
90
+
Once you apply these steps, your Document form will look something like this:
*The Document form, with custom styles applied. It still needs some manual adjustments.*
94
+
95
+
Though you've applied your custom styles to the Document form, it still needs a little tweaking before it's ready for end users. Creating whitespace between fields and grouping similar fields will make the form more user-friendly.
96
+
97
+
If you want to create a "field group" as shown in this project, you can create an HTML field with a div and the "user_group" or "info_group" CSS classes. You can also add these classes to existing fields, like the item_info field.
98
+
99
+
>Note that these field groups only group fields *visually* - the fields "inside" these boxes won't drag like if they belonged to a groupbox field.
100
+
101
+
Here's an example of what your final Document form could look like:
0 commit comments