Restriction of Workflow.
Hi,
I am standar workflow for PO release with little bit customization. Its working fine. Now I need to restrict, the work flow for only some document types. Ex: EKKO-BSART = 'NB' then workflow should be triggered for only type NB.
Please help me out.
Regards,
Chandra.
Check transaction SWEC (linkage).
PO is EINKBELEG (BUS2012).
Then select the line that triggers the workflow (check the event). Then you can double-click on field-restrictions to add your conditions.
I hope it is what you need!
PS. If that does not solve the problem check Transaction SWETYPV (Type linkages). Find your Object/Event/Receiver type and doubleclick. You can create a check function, excluding certain types.
Similar Messages
-
Restrict Workflow Administrator responsibility for a business group
My requirement is to restrict the Workflow Administrator responsibility to a specific business group so that the administrator can view all notifications/transactions for a given business group only for ALL item types. I tried following the steps given in the document 'Oracle Self-Service Human Resources (SSHR) Release Notes, Release 12.1.1' metalink id 578360.1. However, it doesnt seem to be working. Any idea on how to do this configuration?
Thanks,
PallaviHi,
EBS version: 12.1.3, Database 11g
Below are the steps to reproduce the issue:
1) Create a security profile 'XXX-UK-WF' with following values:
Business Group: <UK business group name>
View Employees: Restricted
View Contingent Workers: Restricted
View Applicants: restricted
View Contacts: Restricted
View Candidates: All
Organization Security Tab--> Security Type: View All Organizations(No Security)
2) Set the HR: Security Profile option at the responsibility level for the Workflow Administrator Web(New) responsibility.
3) Log on to the Functional Developer responsibility and search for the predefined Workflow Item Attribute Values (WF_ITEM_ATTRIBUTE_VALUES) object.
4) Click the Update icon to navigate to the Update Object page.
5) Click Create Grant on the Grants tab.
On the Define Grant page, enter the following details:
In the Name field, enter a descriptive name for the grant.
Specify the effective date for the grant as '01-Sep-2011'.
In the Grantee Type field, select 'Group of users' and select teh responsibility 'Workflow Administrator Web(New)' in the Grantee field.
6)In the Object field, select the delivered object Workflow Item Attribute Values
7)On the Grant: Select Object Data Context page, select the HR Self-Service Selected Person ID Instance Set (HRSS_WF_ATTR_PERSONID_INSTSET)
8) On the Grant: Define Object Parameters and Select Set page:
In the Set field, enter the delivered Business workflow item attribute permission set (WF_ADMIN_ITEM_ATTR_PSET).
Click Finish to complete the grant creation process.
9) Logout and login as a user having Workflow Administrator Web(New) responsibility. Navigate to Administer--> Status Monitor. Search for all the workflows started this week. All the transactions from all the business groups will be listed. ideally, only the transactions occuring in UK business groups should have been listed. -
How to schedule a workflow for recurring executions: The solution
Scheduling a workflow for recurring execution has been long awaited in WFA, perhaps from 2.0 time. The following document shows how to get it done. I've also explained the logic behind it. It’s very simple to use, meets every requirement which one can have from a scheduler and of course highly flexible. Let's go!! The Real stuff. What is this? Is this actually a scheduler? No. This is actually a command in your workflow, but a special 'magical' command. This 'magical' command logic is built using the answers for the following questions: Can a workflow be scheduled for a delayed execution in a future time? Yes, but only one execution instance. If you want the next execution, execute the workflow again providing the same set of inputs and the execution date/time.During workflow execution, can a command inside a workflow get to know what is the name of the workflow? YesDuring workflow execution, can the command know what is the job execution id? YesIs there any programmatic interface available to know what are the user input provided or a particular job execution? YesCan a command inside a workflow trigger another workflow? Yes.Can a command inside the same workflow trigger itself? Absolutely yes. I've ticked all boxes needed to build such a solution. The solution is to make the workflow a smart workflow, so smart that it can schedule itself for the next execution. It no longer needs any other task scheduler to tigger it. WFA provides a large set of REST APIs for other 3rd part SW integration. But I also can make good use of these APIs to make smart workflows. I have always believed that WFA should not only be seen as a framework for automating Storage boxes or server, but just about any task( inside a computer of course) which is done manually. WFA is an awesome product indeed. So this is a command called "Workflow Scheduler" which you can put in your workflow as another command. Prerequisites: You need PowerShell 3.0 on your WFA server. I certainly could have done it for PoSH2.0 as well, but life for web interfaces using PowerShell is so much easier with Posh3.0. Posh3.0 is a big jump from 2.0. WFA is fully supported to work on Posh3.0. Its available by default in Win2012, Win2008 can be upgraded, Win2003 users can't use it. Add credentials of a WFA Admin/Architect in you WFA itself with Name/IP: localhost Match: ExactType: OtherName/IP: localhostUsername: <WFA Admin/Architect Username>Password: <User Password> 3. Minimum WFA version 2.2. This is only needed for Importing the dar. I've provided the command code in text too. The command code is the real deal. How to use it? If you have a workflow which you want for recurring executions, just add this command "Workflow Scheduler" in it. The command takes parameters for the workflow execution intervals. For example minsInterval for executing this workflow every x minutes, or daysInterval for executing the workflow etc.Now just like a normal workflow execution execute this workflow deciding what is the trigger time. Example: Suppose you want the execution every day at 10:00 PM.So provide daysInterval = 1 And execute the workflow for a delayed execution at 10:00 PM. You can pick the day to start as you wish. The workflow will execute at 10:00 PM and when this execution reaches our magical command "workflow scheduler", this command will trigger the same workflow with same set of inputs for the next execution at 10:00 PM tomorrow. And so on an so forth. I’ve attached a very simple example workflow here to help you understand. An Example of a workflow scheduled for recurring execution Daily at 11:30 PM starting 10-March-2015 How to stop/suspend this recurring execution? Easy. You just abort the next scheduled job execution in Execution=> Execution Status. The cycle will stop. How to resume it? Easy again. Just resume the same aborted job. The cycle restarts. Can I change the schedule execution time? Yes. After aborting the current execution, you can resume the same workflow at a new time. Execution interval can't be modified as you can't change the command parameters. But the recurring execution now can occur at a new time. Where or which position to place this “workflow scheduler” command in your workflow? At the beginning ? At the end? Or somewhere in the middle. This completely depends on your choice. See some below cases. You don't want the next job execution scheduling to happen if any of the commands in my current workflow execution fails: Put command “workflow scheduler” in the end. It will trigger the schedule of the next job execution only when all real original commands of your workflow have passed. else not. You want continuous job executions irrespective of the workflow command failures: Put it in the beginning. It will trigger the schedule for next execution before any of the actual command begin executing. You want an approval before the next execution job is scheduled: Add an approval point before the comamnd. So it’s all left to you. Can an operator decide the execution schedule? Yes, but which workflows will be available to him/her for this recurring execution will have to be decided by the designer. This is a good thing to have as it serves for access control in a way. The Architect/Admin can now restrict which workflow can be put for recurring executions. Operators can’t execute just any workflow available to him for automatic recurring execution. And the workflow designer can also choose which scheduling parameter is to be made a variable for the operator. For example the designer want the operator to schedule a given workflow only for weeks Interval and not months or days i.e. he/she can only chose to schedule for weekly, biweekly etc. executions and nothing else. For this the designer can define a User-Input variable only for weeksInterval parameter. It’s Done. You want workflow execution to be scheduled either for daily or once in 2 days but not any other. You can restrict this. Or he/she wants to give full freedom to the operator make his/her own decision about scheduling, he defined user-input variable for all scheduling parameters. The workflow designer wants weekly schedule but the day should not be a weekday: You can even do this. Is this flexible enough for my requirements? I’ve attached the very command code. You can modify the command as per your requirements. Suppose you want daily execution of a certain workflow at 10:00 PM but skip a day of execution if the day is a Monday. Modify the code check for the day and add another day if it’s a Monday. Its posh code and highly readable. So you can see how this can be used in a variety of ways. This is the beauty of a programmatic solution. Its highly flexible, it allows users to design solution based on their requirements. Flexibility is the heart & soul of WFA. Thats why I like it. I have a workflow but I don't want to modify it by adding a new command in it. Can I still use this solution? Yes but with WFA 3.0 on wards. WFA3.0 allows to create modular workflows. Create a parent workflow with you actual workflow as a child workflow in it. Add our “workflow scheduler” command too. So now you don't need to touch your existing workflow. I've attached a workflow example here. Have fun!! sinhaa
Providing a new version 1.1.0 of the command "WFA Schedular" Changes made: Added conditional String Representation based on the Scheduling parameter provided. Provided check for the right number of parameters passed into the command.Added a new parameter "Expiry Date" to automatically stop the recurring execution upon expiry.Check for Posh3.0 version in code.Have Fun!! sinhaa Below example for:Schedule a workflow for recurring execution every alternate day i.e. once in 2 days at 10:30 PM starting 06-Jul-2015 (Today's date is 02-Jul-2015) . The recurring workflow execution should expire on 31-Dec-2015 and stop.
-
Workflow does not start automatically on create item (yet another time)
The topic has been discussed broadly throughout different forums, but I didn't find the solution to my issue yet and hope you can help me out with ideas to sidestep the difficulties created by Microsoft.
I have one list 1 in Site Collection A, and one list 2 in Site Collection B (PWA site collection). I need to copy an item from list 1 to list 2 with some values. I use a "Call http web service" action to accomplish
that as I need to copy informatin cross site collections.
The "Call webservice" is in an App Step, because the user creating an item in list 1 does not have permissions on list 2. Thus, my item is created "by workflow" (not "by System Account") in list 2. Now I need a second
workflow to start on list 2 which will create a project in Project Server.
As I am working across 2 site collections, I can not use a SharePoint 2010 workflow with impersonation step for list 1 as the "Call a webservice" action is not available for SP2010 workflows and "Copy item" only works in the same site.
In Nintex I can impersonate the web service call - is this also somehow possible for SPD2013 workflows? Or is there any other possibility to get over this silly restriction of workflows not starting automatically on System account created items? Someway
perhaps to tweak the App Step in impersonating with another user account?
Any help appreciated!
I really can't understand, that this common requirement is still not solved by Microsoft :-( I found more threads on the topic than I can count, so this seems to happen quite often... at least they should finally offer a proper way of doing some kind
of impersonation with the calls so we have a chance to change the creating user account.Hi,
As I understand, you would like to use workflow to copy list items cross site collection.
So far it is not supported with OOB workflow option, here is an codeplex workaround:
https://spdactivities.codeplex.com/wikipage?title=Copy%20List%20Item%20Extended%20Activity
Please check if it can be help.
Regards,
Rebecca Tu
TechNet Community Support -
SRM PO Workflow (BADI Type) in waiting status
Hi all,
I am in SRM extended classic scenario. After shopping cart gets created, it gets automatically approved and PO is created. Then PO workflow is triggered for approval. This happens fine in development box. However when its been transported in quality, the PO workflow remains in 'Waiting Status'. The requested start date has been set to future date 31.12.9999. Thus the workflow does not start properly. If gets stuck with the first step. It does not go upto the approval step.
Is there anyone who can tell me why this is happening and what is the remedy?
Regards
DipHi Dipankar,
Is it required to set the requested start date to future date 31.12.9999?
Also check if the same has been maintained in development system.
I think this might be restricting the workflow to proceed. Please check the relevance of this deadline monitoring.
Regards,
Saumya -
Control Workflow Report output using Structural Authorization
Is it possible to control output of Workflow Reports using Structural Authorizatins. E.g. Workflow Admins having access to tcode SWi2_FREQ will be able to see project wide data, but i want to restrict the workflow admins at department level from seeing workflow data for other departments. is that possible using Structural authorizations or any other mechanism?
My understanding is that Structural authorizations pretty much control PA/PD, and not other modules. I did a quick test,
1) Created a org structure
2) Created employees, users, and set up structural authorizations
Now when users are granted authorization to PA20, they are restricted to what they should be seeing, but when they are granted authorization for workflow admin reports, structural authorization don't seem to work, they are able to see data for workflow triggered for other departments as well. Is that the standard behavior or i am missing something. I don't have enough experience with Structural auth.
I will appreciate any guidance on this matter.
Thanks,
SaurabhArghadip, please explain how this will prevent someone from Norway from looking at the workflow log of a workflow for an employee belonging to the Danish part of the organisation.
<i>Message was edited by Kjetil Kilhavn:</i>
To explain a bit more in detail: how does this prevent me (Norwegian) from going into SWI1, SWIA or any other transaction, and looking at data from other parts of the organisation. I don't think it will work.
I think the only way to achieve this is to either modify SAP's standard code and include some structural authorisation checks - or take the standard transactions out from every user role and create your own wrappers or program copies which basically does the same as the modification would have to do. -
Multiple Status Restrictions in BSVW
Hi Experts,
I want to trigger a workflow whenever a Maintenance order user status has been changed to some other staus.
For this I have created a subtype Z_BUS2007 of BUS2007 and added that an event STAUSCHANGED to that subtype.
I have also delegated the same. After that, in BSVW transaction I have added a row using StatusOT as ORI, Schema as WMSTATUS, BusinessOT as BUS2007 and event as STATUSCHANGED.
I have used this event to trigger my workflow. When I gave one staus restriction the workflow is being triggred but it is not working when i am giving multiple status restrictions.
Please help.
Regards,
HariomHello Hari !
I developed a workflow for the same scenario.For this scenario, I didn't configure any thing in BSVW.
Instead I created an event "CHANGED" in ZBUS2007 and delegated to BUS2007.You can define the status restrictions with respect to triggering the workflow either using a check function module or creating s database attribute(Table : JEST, field : STAT).
Still, if you want to use BSVW, the configuration required is :
Status OT : ORI,Business OT : BUS2007, Event : CHANGED, Name : Changed
Regards,
S.Suresh. -
Hi,
I need to restrict a workflow based on certain plants. Currently these plants are maintained in the plant table but our requirement is to check the plant conditions without using the plant table.
Kindly let me know your suggestions.
Regards,
Esha RajHi Esha,
Based on plants you can decide whether workflow should trigger or not
for that you could use a Function Module and use that function module to trigger the workflow
the logic inside the Function Module should be like fetch all the plants from the table and according to the plant value you could trigger the workflow using SAP_WAPI_START_WORKFLOW.
that's the case if you want to decide the triggering of workflow
suppose the workflow is triggered and you need to build your logic inside the workflow
Put a condition with two outcomes True and False
if plant value satisfy ur need then you can proceed with your workflow(true)
else put a process control step 'Stopped' and choose cancel workflow
(including all callers) likewise you could stop your workflow if your condition doesnt satisfy your requirement.
Kind Regards
Hari Sankar M -
Hi,
i have used two BO's in my workflow , also i have added decision step in that workflow,
if i choose yes then the second BO should be functioned, while passing through the container ,
we found out that first BO works perfect, all values in Bo were present, but in Second BO we
cannot find any values ... is there any restriction that workflow should have only one BO????
or is there any option to be selected while using multiple Bo's?
kindly advise on this.
Regards,
Dinesh RHi,
To get values ( attributes) in the business object, you need to instantiate the BO.
Here probably you are instantiating the First BO but not the second one. You can use
BO: SYSTEM and method 'GenericInstantiate' to create instance of any BO type . There is no restriction of using
multiple BOs in a single workflow.
Regards
Kedar -
Start workflow only after specifc transaction
Greetings,
I've got a workflow that updates the minimum target quantity for an article.
I want to restrict this workflow to execute only on a specific transaction.
Please advise how to bind/pass SY-TCODE into a workflow
Thanks,
Doug -Hi,
You have to Restrict Via Start Condition
You have to create a attribute, in the attribute you have to write a code, for that t.code Set the flag 'X' else null.
To Give the start Condition See the step 3.2 in this [link|https://wiki.sdn.sap.com/wiki/x/aYDUAw ] .
Regards,
Surjith -
Hi Guys,
The PO creation and Goods Receipt are done in one WF after Sales order has been created.
There is one more workflow start event linked to PO event (REALEASESTEPCREATED).. I need the control the WF triggering in this case. BO BUS2012.
Is there a way I can restrict the workflow by giving some other condition ?
CheersHi,
Good Receipt has been done in two workflows for two different requirement.
One workflow creates PO and GR after SO has been created.
Second workflow also for GR creation and series of other task as well.
These are involved in a different biz process.
I want to control the 2nd workflow triggering, so that when the first workflow creates PO, I dont want the 2nd workflow also get triggered.
2nd workflow has been called through different biz process ! when supplier PO has been created..
Cheers -
Event creation with status management
Hello esteemed gurus ... it's your friendly workflow noob again
It seems once people get a sniff that there is a someone who knows a bit about workflow in the company, everyone wants a piece of you!
So... I have been asked to setup a workflow that will trigger when a user changes a user status on an SD contract. I've done some reading and I believe I'm nearly there but need a little help ...
I have setup event creation with transaction BSVZ for object category VBK, specified my status profile, and business object BUS2034 and I'm using the event "CHANGED", within this I have set a status restriction to particular status of my user status profile.
In my workflow definition I have specified the start event "CHANGED" for my business object BUS2034.
The thing is, the workflow starts for every change to the contract, whereas I was expecting it to only start when the particular status I defined in my status management was set in the contract header.
Are there any additional settings I need to make in order to restrict the starting conditions of the this workflow?
Many thanks once again.
NeilHi Neil,
There is two options to restrict the workflow.
First one is start condition. You can check the workflow log. If your required field is populated in the Workflow container you can use start condition to restrict the workflow. In the Basic data of workflow template, Start condition is there. You can use the condition editor to set the condition.
If your field is not populated by default, then you can use check function module for this. You need to create one FM, and in transaction swe2, the FM needs to be Configured. The concept is, based on the Sales document number you can get the required field and check the condition inside the FM. If the condition satisfied just leave it. The workflow will be triggered. If the condition is not satisfied raise a Exception. So that the Workflow will not be triggered.
Thanks,
Viji. -
Issue in Check Function Module
Hi All,
Am doing a custom Workflow for Goods Movement.
In my Workflow am using the Triggering event "created" of Business Object "/SAPCEM/02".
I need to trigger my Workflow only for specific "Movement Type" (Eg. 551).
The Event Container is having only the values Material Document & Year. I have created a check function module in which I built the logic to get the MovementType(BWART) from table MSEG for the Material Document & raising exception in case of other than 551.
But the function module is not working as I expected. The problem is the MSEG table is not getting updated with the new Material Doc, while the Check Function Module is being called. (MSEG is updated after Check FM, it seems). So no record in MSEG for our MaterialDoc during the call to check function module. So the query always fails.
I need to restrict my workflow for specific Movement Types(MSEG-BWART).
Could you please advice me in this ?
Regards,
Anbarasan KI have absolutely no idea if this works, but you could try to place a check FM on the event only in transaction SWEINST with a wait up to 1 second statement in it.
Maybe, just maybe then you can properly use the check FM on the event-->WF in SWE2.
Alternatively if you are of the opinion that the data should be updated when the event is triggered you could raise an OSS message (obviously search OSS first to see if this has come up previously)
Kind regards, Rob Dielemans -
BUS1065 - SAP HCM - Employee changes in infotype 0000 + infotype 0001
Dear all,
I have a problem with the customizing in order to recognize the changes in infotype 0000 + infotype 0001 for employees.
What do I want?
If there is a new hire, a rehire, a retire or a company-left action, I want to start ONE workflow in order to dispatch the employee data to several satellite systems considering the new validity dates.
What happens currently?
I maintain a rehire action through transaction PA40 and the system raises several events so that the workflow start multiply, meaning raises event hired, rehired, companyleft, ...
My customizing:
TCode: SWETYPV
BO BOR-Objekttyp BUS1065 COMPANYLEFT WS91000007 0
BO BOR-Objekttyp BUS1065 HIRED WS91000007 0
BO BOR-Objekttyp BUS1065 POSITIONCHANGED WS91000007 0
BO BOR-Objekttyp BUS1065 REHIRED WS91000007 0
BO BOR-Objekttyp BUS1065 RETIRED WS91000007 0
TCode: SWEHR1
P Person 0000 BUS1065
P Person 0001 BUS1065
TCode: SWEHR2
P Person 0000 Maßnahmen APP 100 BUS1065 CACS_LOG_HRINFTY
P Person 0000 Maßnahmen DEL 100 BUS1065 CACS_LOG_HRINFTY
P Person 0000 Maßnahmen INS 0 BUS1065 HR_EVENT_RULES_PA0000
P Person 0000 Maßnahmen INS 100 BUS1065 CACS_LOG_HRINFTY
P Person 0000 Maßnahmen UPD 0 BUS1065 HR_EVENT_RULES_PA0000
P Person 0000 Maßnahmen UPD 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun APP 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun DEL 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun INS 0 BUS1065 HR_EVENT_RULES_PA0001
P Person 0001 Organisatorische Zuordnun INS 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun UPD 0 BUS1065 HR_EVENT_RULES_PA0001
P Person 0001 Organisatorische Zuordnun UPD 100 BUS1065 CACS_LOG_HRINFTY
TCode: SWEHR3 (For testing purpose only one entry)
P Person 0000 INS 1 BUS1065 HIRED
Can anybody tell me how I can customize our system so that the system raises only event hired for a new employee hire and e.g. companyleft event for a termination action?
Thx you all in advance for your support!!!
In case you need more information, don't hesitate to contact me!
Kind regards,
AndréHi
TCode: SWETYPV
BO BOR-Objekttyp BUS1065 COMPANYLEFT WS91000007 0
BO BOR-Objekttyp BUS1065 HIRED WS91000007 0
BO BOR-Objekttyp BUS1065 POSITIONCHANGED WS91000007 0
BO BOR-Objekttyp BUS1065 REHIRED WS91000007 0
BO BOR-Objekttyp BUS1065 RETIRED WS91000007 0
Iam not sure about what you have done in the customizing but, the above settings represents that the same workflow is set as receiver for different events.
Now As per my understanding what ever you have posted, I feel like you want to restrict the workflow intiiation only for some of the events. and for the remaining events you do not want to start the workflow.
If this is the case then I would suggest that to over come any kind of issues, I suggest you take a copy of the workflow WS9100000070 and assign the new workflow template to each different event, in this way you can differentiate which workflow is acting as a receiver for the event.
and accordingly you activate the Event Linkages in SWE2 txn too.
Regards
Pavan -
Task executions in multi server environment
Hi All,
I have a question regarding the task execution in a multi-server environment.
Below is the scenario:
We have two SIM applications: one for intranet users (employees and contractors) and one for extranet users (customers). Both these applications point to same database repository.
Intranet : idm-intra.ear ( this is deployed on IntraServer1 and IntraServer2)
Extranet: idm-extra.ear ( this is deployed on ExtraServer1 and ExtraServer2)
And both share same repository WAVESET.
Now we are deploying some request workflows for intranet users. In our case even the extranet application can see these tasks.
My question is: if I triggered a request workflow from intranet application and it is pending for approval and when it times out, is there a chance that this workflow is executed by the "extranet" application?
Thanks,
kIDMan.The answer to your question is yes. If you go to the Configure>>Server tab in the admin console on any of these instances of IdM you should see all four instances. An easy way to test this is happening, is to enable workflow tracing and launch a couple of request from IntraServer1. IdM will try to distribute the work among all the servers it knows about so you'll see portions of the flow within the workflow traces on the individual servers. Well maybe it's not an easy thing to test because it's a timing issue.......
I had an issue recently in which the guy doing the build to the QA environment messed up and pointed the QA IdM instances to the DEV repository. We were doing some testing of some flows on DEV and they were being executed on the QA IdM instances and bombing out with ClassNotFound errors because the QA environment was not build out completely/correctly. So even though the requests were being launched from the DEV instances they were being executed on the QA instances.
There is a feature that is supposed to let you restrict which workflows run on which servers. If you go to the admin console and click on Configure>>Servers choose a server and click on the 'Scheduler' tab and then check the 'Task Restrictions' checkbox. From here you can restrict which workflows run on which servers. But my suspicion is that this doesn't work correctly (based on some testing I was doing on 7.1)....might want to test it out....Hope this helps.
Maybe you are looking for
-
I have a Nokia 97 mini what is the best way to connect it to my new Mack Book Pro
Hi All Mac Book Pro users, I have just purchased a new Mac Book Pro and it has Lion V10.7 I am trying to connect my Nokia N97 Mini. has anybody out there managed to achieve it and HOW DID YOU MANAGE IT. Any help will be gratefully accepted, Thanks st
-
Zen Vision M (60GB) and supported devices (USB Host Featu
I would know if Canon Powershot A520 is a supported device by USB Host Feature. thanks mat
-
Wrong photos/videos reading in About This Mac - Storage Tab
I have updated to Photos from iPhotos but now when i hit about this mac and storage reading ... i get it all messed up it shows 1GB of photos where i have at least 20GB .. is there any way to fix this ? before i used to re-index the database but i do
-
Does Elements save settings in a way that is visible to us?
When I change a setting in PSE, such as adjusting Hue to, for example, +20, or when I add, for example, a blue photo filter, it appears that PS E does not display the change after applying it. It appears this way to me because, when I go back into Hu
-
HI All, I have made changes in R/3 data source for 2LIS_13_VDITM and successfully transported to test server. Strangely when I replicate I could see the text of this data source in Dev system is missing. I tried to add the text in RSA6 change mode bu