Skip to content

Commit 024e99b

Browse files
committed
Merge branch 'feature/update-readme' into develop
2 parents 1cd4389 + 89a4b2f commit 024e99b

File tree

5 files changed

+56
-16
lines changed

5 files changed

+56
-16
lines changed

LICENSE.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
The MIT License (MIT)
33

4-
Copyright (c) 2017 Aras Corporation
4+
Copyright (c) 2018 Aras Corporation
55

66
Permission is hereby granted, free of charge, to any person obtaining a copy
77
of this software and associated documentation files (the "Software"), to deal

README.md

Lines changed: 55 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,26 +2,27 @@
22

33
This project demonstrates how to customize form field appearance with custom CSS.
44

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
116

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.)
148

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.
1710

18-
> Though built and tested using Aras 11.0 SP7, this project should function in older releases of Aras 11.0.
11+
## History
1912

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.
17+
[v1.0](https://github.com/ArasLabs/custom-form-css/releases/tag/v1.0) | Initial release.
2118

22-
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
2320

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.
21+
Project | Aras
22+
--------|------
23+
[v1.2](https://github.com/ArasLabs/custom-form-css/releases/tag/v1.2) | 11.0 SP9, 11.0 SP7, 11.0 SP5
24+
[v1.1](https://github.com/ArasLabs/custom-form-css/releases/tag/v1.1) | 11.0 SP7, 11.0 SP5
25+
[v1.0](https://github.com/ArasLabs/custom-form-css/releases/tag/v1.0) | 11.0 SP7, 11.0 SP5
2526

2627
## Installation
2728

@@ -49,6 +50,9 @@ The import package updates the Part form properties to use the custom CSS file a
4950
* Optional: Enter a description in the Description field.
5051
8. Enter the path to your local `..\CustomFormCSS\Import\imports.mf` file in the Manifest File field.
5152
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.
5256
10. Select Type = **Merge** and Mode = **Thorough Mode**.
5357
11. Click **Import** in the top left corner.
5458
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.
5761

5862
## Usage
5963

64+
### Viewing the Styled Form
65+
66+
![Customized Part Form](./Screenshots/custom_part_form.PNG)
67+
6068
1. Log in to Aras as admin.
6169
2. Click **Design > Parts** in the table of contents (TOC).
6270
3. Open an existing Part, or create a new Part to view the customized Part form design. It should look something like this:
6371

64-
![Customized Part Form](./Screenshots/custom_part_form.PNG)
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+
![Document Form](./Screenshots/document_form.png)
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:
91+
92+
![Half Styled Form](./Screenshots/half_styled_form.png)
93+
*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:
102+
103+
![Styled Document Form](./Screenshots/styled_document_form.png)
104+
*The Document form, with custom styles and manual spacing adjustments.*
65105
66106
## Contributing
67107

Screenshots/document_form.png

115 KB
Loading

Screenshots/half_styled_form.png

119 KB
Loading
128 KB
Loading

0 commit comments

Comments
 (0)