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

Is it possible to associate two or more workflows to the same Item type ?

Ambuj — Wed, 02 Jun 2021 08:47:02 GMT

I am new to Aras.

My question is:

Is it possible to associate two or more workflows to the same Item Type?

At the time of initiating the workflow, how one can pick one of the several workflows?

Secondly, using code is it possible to pause a workflow for some time (say 4 minutes) before it executes the next step?

Thanks,

Ambuj

Discussion Starter I

Thu, 24 Jun 2021 13:13:15 GMT

Start a discussion in a forum that receives 5 replies.

Is it possible to create Dependent List of Values after creation of a group?

Ambuj — Thu, 03 Jun 2021 03:46:39 GMT

Once the group is created on the Form, is it possible to make the dropdown list of values from first drop down to be filled in automatically based on the other dropdown list of values?

Thanks

Ambuj

Connect Aras Innovator12 with Java web Application issue

Ashok.Yadav — Thu, 03 Jun 2021 04:08:00 GMT

Hello Guys,

I want to connect Aras Innovator 12 With my Java web Application is not work. when I try connect Aras Innovator 11 with my Java web Application is work. I am using same code in case of Aras Innovator 11 and 12 . Why I am getting Strange behavior . I do not know.

Please help me . code is below and Exception is below.

httpConnection: Exception :======java.io.IOException: Server returned HTTP response code: 401 for URL: win-8dg8qc6q2gp:80/.../InnovatorServer.aspx

import java.io.IOException;
import javax.servlet.ServletException;
//import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.nio.charset.Charset;
import java.io.ByteArrayInputStream;
import java.util.Vector;
import javax.swing.JOptionPane;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.MimeHeaders;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPMessage;
import org.w3c.dom.NodeList;

/**
* Servlet implementation class ArasInnovatorLogin
*/
//@WebServlet("/ArasInnovatorLogin")
public class ArasInnovatorLogin extends HttpServlet {
private static final long serialVersionUID = 1L;
String ErrString="",invalideDb="",ErrorUi="";
java.io.BufferedReader in;
String database="",userName="",innovatorServer="",request="",password="";
NodeList list=null;
boolean isSuccess = false; NodeList returnList;NodeList innerResultList;

/**
* @see HttpServlet#HttpServlet()
*/
public ArasInnovatorLogin() {
super();
// TODO Auto-generated constructor stub
}

/**
* @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse response)
*/
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
// TODO Auto-generated method stub
//response.getWriter().append("Served at: ").append(request.getContextPath());
}

/**
* @see HttpServlet#doPost(HttpServletRequest request, HttpServletResponse response)
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
// TODO Auto-generated method stub
try{
Vector getItem=null;
ErrString="<SOAP-ENV:Envelope xmlns:SOAP-ENV='schemas.xmlsoap.org/.../'><SOAP-ENV:Body><SOAP-ENV:Fault xmlns:af='www.aras.com/.../faultcode><faultstring><![CDATA[Authentication failed for admin]]></faultstring><detail><af:legacy_detail><![CDATA[Authentication failed for admin]]></af:legacy_detail><af:exception message='Authentication failed for admin' type='Aras.Server.Core.InnovatorServerException' /></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>";
invalideDb="<SOAP-ENV:Envelope xmlns:SOAP-ENV='schemas.xmlsoap.org/.../'><SOAP-ENV:Body><SOAP-ENV:Fault xmlns:af='www.aras.com/.../faultcode><faultstring><![CDATA[The Database is not available.]]></faultstring><detail><af:legacy_detail><![CDATA[The Database is not available.]]></af:legacy_detail><af:exception message='The Database is not available.' type='Aras.Server.Core.InnovatorServerException' /></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>";
ErrorUi="<SOAP-ENV:Envelope xmlns:SOAP-ENV='schemas.xmlsoap.org/.../'><SOAP-ENV:Body><SOAP-ENV:Fault xmlns:af='www.aras.com/.../af:legacy_detail><af:exception message='formation' type='Aras.Server.Core.InnovatorServerException' /></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>";
this.innovatorServer ="">win-8dg8qc6q2gp:80/.../InnovatorServer.aspx";
this.database ="Netradyne";
this.userName =request.getParameter("UserName");
this.password =request.getParameter("password");
response.getWriter().println("userName:" +userName);
response.getWriter().println("password:" +password);

this.request = "<AML>"
+"<Item type='User' action='get' select='user_name,password'>"+
"</Item>"+
"</AML>";
String formation="Authentication failed for"+" "+this.password;
String nameSpace = "">http://www.aras-corp.com/";
String remoteMethod = "ApplyAML";
String characterEncoding = "UTF-8";
String SOAPmessage = "<SOAP-ENV:Envelope xmlns:SOAP-ENV='schemas.xmlsoap.org/.../' encodingStyle='">schemas.xmlsoap.org/.../encoding'>"
"<SOAP-ENV:Body>"+
"<"+remoteMethod+" xmlns:m='"+nameSpace+"'>" + this.request + "</"+remoteMethod+">"+
"</SOAP-ENV:Body>"+
"</SOAP-ENV:Envelope>";
// Create new URL object and HttpURLConnection object
java.net.URL url = new java.net.URL(innovatorServer);
java.net.HttpURLConnection httpConnection = (java.net.HttpURLConnection) url.openConnection();
// Convert the message to a byte array
byte[] messageBytes = SOAPmessage.getBytes();
//response.getWriter().println(messageBytes);
// Set headers
httpConnection.setRequestProperty("Content-Length", String.valueOf(messageBytes.length));
httpConnection.setRequestProperty("Content-Type","text/xml; charset=" + characterEncoding + "\"");
httpConnection.setRequestProperty("SOAPAction", remoteMethod);
httpConnection.setRequestMethod("POST");
httpConnection.setRequestProperty("AUTHUSER",this.userName);

httpConnection.setRequestProperty("AUTHPASSWORD", MD5(this.password));

httpConnection.setRequestProperty("DATABASE",this.database);
httpConnection.setDoInput(true);
httpConnection.setDoOutput(true);
// Write and send the SOAP message
java.io.OutputStream out = httpConnection.getOutputStream();
response.getWriter().println("httpConnection:" +out);
out.write(messageBytes);
out.close();
// Read server response

in = new java.io.BufferedReader(new java.io.InputStreamReader(httpConnection.getInputStream()));
String inputLine; String erroS="";
while ((inputLine = in.readLine()) != null) {
erroS=inputLine;
MessageFactory factory = MessageFactory.newInstance();
SOAPMessage message = factory.createMessage(new MimeHeaders(),new ByteArrayInputStream(inputLine.getBytes(Charset.forName("UTF-8"))));

SOAPBody body = message.getSOAPBody();
NodeList returnList = body.getElementsByTagName("Item");
isSuccess = false;
response.getWriter().println(in.readLine());
for (int k = 0; k < returnList.getLength(); k++) {

NodeList innerResultList = returnList.item(k).getChildNodes();
response.getWriter().println("innerResultList.getLength()="+innerResultList.getLength());
for (int l= 0; l < innerResultList.getLength(); l++) {

isSuccess=true;
String or="'";
char nr='"';
String Nr=String.valueOf(nr);

//erroS.replaceAll(or,Nr);
//response.getWriter().println(erroS.replaceAll(Nr,or));
//response.getWriter().println(ErrorUi.replaceAll("formation",formation));

int flag=1,Flag=0;
if( ErrString.equals(erroS.replaceAll(Nr,or)))
{
flag=0;
Flag=1;
response.getWriter().println(password+" is not valide Password");

}
if(invalideDb.equals(erroS.replaceAll(Nr,or)))
{
flag=0;
response.getWriter().println("Authantication is fail for the Selected DataBase"+" "+""+database);

}

if(ErrorUi.replaceAll("formation",formation).equals(erroS.replaceAll(Nr,or)))
{
flag=0;
if(Flag!=1)
response.getWriter().println(userName+" "+" is not valide user");
}
if(flag==1)

{

}

// getItem=new Vector();
if (isSuccess) {
list = body.getElementsByTagName("Item");
response.getWriter().println("isSuccess==="+isSuccess);

}
}

}

}
}
catch (Exception e) {
// TODO Auto-generated catch block
response.getWriter().println("Exception :======"+e);
e.printStackTrace();
}
doGet(request, response);
}
public static String MD5(String s) throws Exception{
java.security.MessageDigest m = java.security.MessageDigest.getInstance("MD5");
m.update(s.getBytes(),0,s.length());
return new java.math.BigInteger(1,m.digest()).toString(16);
}

}

Thanks in Advance

PDF and Image file handling

schauhan — Mon, 15 Mar 2021 19:52:11 GMT

Hi,

On my latest installation of Aras open (12 SP9) clicking on pdf and image file (png, jpeg, etc) Files attached to Document item type automatically downloads it. Changing Chrome setting related to how PDF files are handled or using different browsers seems to have no effect.

I would like PDF and image files to open in a separate browser window as it did on an older installation of Aras 12 SP0. Are there any server related settings that control how these file types are handled out of box?

Thanks.

-Sam

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.

Ask A Question I

Wed, 02 Jun 2021 08:47:02 GMT

Ask a question in a forum.

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